vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQs 

Frequently asked questions about Activity Tracker Event Routing.



 What are the different ways to manage auditing events? 

Activity Tracker Event Routing offers 2 different ways to manage auditing events in an IBM Cloud account. You can use Activity Tracker, an IAM enabled service, to manage auditing events through instances that you provision in each IBM Cloud region where you operate. Alternatively, you can use Activity Tracker Event Routing, a platform service, to manage auditing events at the account-level by configuring targets and routes that define where auditing data is routed. Activity Tracker Event Routing can only route events that are generated in [supported regions](https://cloud.ibm.com/docs/atracker?topic=atracker-regionsregions-atracker). Other regions, where Activity Tracker Event Routing is not available, continue to manage events by using Activity Tracker Event Routing hosted event search.

Activity Tracker routes location-based auditing events to an Activity Tracker instance in the region where they are generated and routes global auditing events to the Activity Tracker instance that is provisioned in Frankfurt.

Activity Tracker Event Routing routes events based on the location that is specified in the logSourceCRN field included in the event. You can define a target, the resource where events are routed to, in any Activity Tracker Event Routing supported region. However, the target resource can be located in any region where that type of target is supported, in the same account or in a different account. You can define rules to determine where auditing events are to be routed by configuring 1 or more routes in the account. You can define rules for managing global events and location-based events that are generated in regions where Activity Tracker Event Routing is supported.

The following table outlines the options to configure Activity Tracker Event Routing per region:



Table 1. Configuration options

 Geo Region Activity Tracker Event Routing hosted event search Activity Tracker Event Routing 

 Asia Pacific Chennai (in-che) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/checkmark-icon.svg)
See [Assembling a team](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-team) for more information about adding users.

If you have a Lite plan subscription, skip this step. You cannot add other users, so you cannot assign anyone to the project manager role. You do not need a separate project manager. As an administrator, you can perform all the tasks that a project manager would typically perform.
6. Click Create.







 What to do next 

After the workspace is created, you can start configuring the workspace resources.

To change the workspace description or workspace name, or to add or remove project managers later, an administrator can edit the workspace. From the Knowledge Studio home page, click the Show menu icon on the workspace tile, and choose the Edit menu option.

Related concepts:

[Uploading resources from another workspace](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-exportimport)

Related reference:

[Language support](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-language-support)





 Tokenizers 

A tokenizer groups characters into tokens, and tokens into sentences. A token is loosely equivalent to a word.

The actions that a tokenizer must take to identify a document's tokens differ depending on the language of the document. In English, tokens are often equated to words as delimited by white spaces in a sentence. However, they do not always match one-to-one with words; other textual elements are considered tokens in some situations. For example, punctuation at the end of a sentence is considered a token, and contractions are often expanded into two tokens. In languages that do not use white spaces, such as Chinese, more complicated statistical algorithms are used to identify the tokens.

The tokenization process is important because it determines the groups of characters that users can highlight for annotation in the ground truth editor.
Like any source code file, you have full traceability of the changes made to a configuration.
* Detect and correct environment drift: If a part of the infrastructure is modified manually outside of the code, it can be brought back in line with the desired state on the next run. [Drift detection](https://cloud.ibm.com/docs/schematics?topic=schematics-drift-note) is a feature of Schematics Workspaces.







 Best Practices 

When adopting IaC for provisioning and configuration management, there are number of recommended practices. These practices are fully supported when using Schematics.



 Codifying everything in IaC 

All the infrastructure specifications should be explicitly coded in a configuration file, for instance as Terraform configurations or Ansible playbooks. The configuration files are the single source of truth of your infrastructure specification and describe what infrastructure components will be used and their configuration?





 Minimize documentation 

IaC is the documentation. With IaC in place, the configuration files represent the documentation and are always up-to-date, which reduces effort. The remaining documentation is about the process. Maintain code in a Version Control System.

IaC configuration files should be kept in a version control systems (VCS), like GitHub or GitLab. This provides an audit trail for code changes, but it also gives the opportunity to collaborate or peer review and test changes before they go live.

With this practice, you can easily track, manage, and revert any potential changes to your systems, with enhanced traceability and visibility.





 Testing 

One of the practices that IaC borrows from software development is testing. Rigorous testing of infrastructure configuration plays a role in reducing post deployment issues. When combined with version control systems, testing can be automatically triggered every time there is a modification in the code.

With Continuous Integration (CI) in place, the template infrastructure configuration can be implemented in multiple environments such as the development, UAT, QA, or production environment with minimal changes applied effectively.





 Modular Infrastructure 

Breaking down infrastructure into [modules](https://github.com/terraform-ibm-modules/documentation) allows for reuse, improved reliability and an easier adoption path. Similar to the use of modules and packages in programming languages.
Storage traffic is to be isolated from other traffic types, and not be directed through firewalls and routers. Keeping the storage traffic in a dedicated VLAN also helps preventing MTU mismatch when Jumbo frames are enabled. For more information, see [Enabling Jumbo Frames](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-jumboframes).

Storage traffic is included in the total network usage of Public Virtual Servers. For more information about the limits that might be imposed by the service, see the [Virtual Server Documentation](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-public-virtual-servers).





 NFS version 

Both NFSv3 and NFSv4.1 are supported in the IBM Cloud® environment. Network File System (NFS) is a networking protocol for distributed file sharing. It allows remote hosts to mount file systems over a network and interact with those file systems as if they are mounted locally.

Use NFSv3 protocol when possible. NFSv3 supports safe asynchronous writes and is more robust at error handling than the previous NFSv2. It supports 64-bit file sizes and offsets, allowing clients to access more than 2 GB of file data. NFSv3 natively supports no_root_squash that allows root clients to retain root permissions on the NFS share.

When File Storage for Classic is used in a VMware® deployment, NFSv4.1 might be the better choice for your implementation. For more information about the different features of each version and what is supported by VMware®, see [NFS Protocols and ESXi](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-8A929FE4-1207-4CC5-A086-7016D73C328F.html).







 Step 2: Submitting your Order
(https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/access-control-read-only.png)

Most buttons, such as Add node, Add folder, and Save new version are disabled. There is no Analytics option in the navigation. The "Try it out" pane is available.
* Writer

This screen capture shows you what someone with Writer service access to a resource sees on the same page.

![Shows the dialog page with buttons enabled, but no Analytics option in nav.](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/access-control-writer.png)

All of the buttons are available. There is no Analytics option in the navigation.











 Common role assignments 



Table 4. Common role assignments

 Goal Instance-level platform role Instance-level service roles Resource-level service roles 

 Make someone a service instance co-owner Administrator Manager N/A 
 Give someone reader access to only one skill or assistant in an instance Viewer, Reader Reader Reader 
 Allow someone to edit and view logs of all the skills and assistants in the service instance Viewer Manager N/A 
 Allow someone to edit a skill or assistant in the service instance, but not view logs Viewer, Reader Writer Writer 
 Give someone full access to only one skill or assistant in an instance Viewer, Reader Reader Manager 



N/A stands for no assignment, meaning no role of the type is assigned.





 Resource-level role impact on available actions 

The Watson Assistant user interface and API comply with the access roles that are defined for a service instance. When someone logs in to the user interface, it adjusts to show only what the current user can access, and it disables functions that the user does not have permissions to do.
(https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-faqibp-v2-faq-cert-mgmt)
* [What languages are supported for smart contracts?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-faqibp-v2-faq-v2-IBP-Overview-1-4)
* [What version of the IBM Blockchain Platform works with the Ansible collection?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-faqibp-v2-faq-ansible-version)
* [How do I get support for running the IBM Blockchain Platform Ansible playbook?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-faqibp-v2-faq-ansible-support)
* [Can the IBM Blockchain Platform monitor the health of a client application?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-faqibp-v2-faq-mon-client-app)
* [Where does IBM store the customer's logs and how long does IBM keep the audit logs for the blockchain platform service?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-faqibp-v2-faq-customer-logs)
* [Do we have access to logging services and what logs are available to me?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-faqibp-v2-faq-v2-Logging-and-Monitoring-11-6)
3. Select Patch Baselines or Extension Baselines depending on what type of update you want to perform on the host. On the Select baseline page of the Remediate wizard, select the baseline group and baselines to apply.
4. Select the target hosts that you want to remediate and click Next. If you chose to remediate a single host and not a container object, the host is selected by default.
5. Optionally, on the Patches and Extensions page, clear specific patches or extensions to exclude them from the remediation process, and click Next.
6. Optionally, on the Advanced options page, select the option to schedule the remediation to run later and specify a unique name and an optional description for the task. The time that you set for the scheduled task is the time on the VCSA. Optionally, select the option to ignore warnings about unsupported devices on the host, or no longer supported VMFS datastore to continue with the remediation. Click Next.
7. On the Host Remediation Options page, from the VM Power state menu, you can select the change in the power state of the VMs and virtual appliances that are running on the hosts to be remediated. A host cannot enter maintenance mode until VMs on the host are powered off, suspended, or migrated with vMotion to other hosts in a DRS cluster. Some updates require that a host enters maintenance mode before remediation. VMs and appliances cannot run when a host is in maintenance mode. To reduce the host remediation downtime at the expense of VM availability, you can choose to shut down or suspend VMs and virtual appliances before remediation. In a DRS cluster, if you do not power off the VMs, the remediation takes longer but the VMs are available during the entire remediation process because they are migrated with vMotion to other hosts.

The selections are as follows:



* Power Off virtual machines - Power off all VMs and virtual appliances before remediation.
* Suspend virtual machines - Suspend all running VMs and virtual appliances before remediation.
* Do Not Change VM Power State - Leave VMs and virtual appliances in their current power state.
If the customer federates their corporate IdP, users from that IdP aren't added to an account as what we might consider a normal user. Instead, users' SAML-based IdP attributes are evaluated at login and if they meet all of the conditions for a trusted profile, they are prompted to apply one or more trusted profiles. Trusted profiles grant users the level of access they need to complete a specialized and specific set of tasks in a limited time-period, for example, 1-4 hours. These are usually critical tasks that you would want to avoid doing unintentionally in daily work. Users don't need to onboard to IBM Cloud, they're automatically added by way of the trust relationship. If a user leaves your company, you can simply delete the user's corporate identity in your directory, which then also revokes access to IBM Cloud. Time-based access allows frequent authentication checks for reduced security risks.
How can I manage migrated billing and support case permissions in IBM Cloud? 

A set of SoftLayer billing and support permissions are now available as migrated permission access groups in IBM Cloud®.

With the initial migration of users and permissions for managing billing and support cases from your SoftLayer account to your linked IBM Cloud account, some users might not have these permissions. However, all migrated permission access groups are now assigned the correct IAM access policies, ensuring that all users are assigned the correct access that they had previously.

  What’s happening 

Users don't seem to have the same managing billing and support case permissions in the IBM Cloud console that they were previously assigned in your SoftLayer account.

  Why it’s happening 

Your migrated permissions access groups might not be assigned the correct access policies when the users were initially migrated.

  How to fix it 

As of 20 May 2019, all [migrated permission access groups](https://cloud.ibm.com/docs/account?topic=account-migrated_permissions) have the correct policies that are assigned for managing billing information and support cases. If you tried to use these groups before this date, the access groups that are missing equivalent IAM access policies might have caused a mismatch in the assigned access between the SoftLayer permissions and IAM access. This is resolved. You can go to Manage > Access (IAM) in the IBM Cloud console, and then select Access groups to review the users and policies that are assigned to each access group.
* [What are the Git repositories that are supported by Blueprints?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-repos)
* [Are variable operators and functions supported in blueprint templates?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-values)
* [How are blueprint module dependencies and execution order determined?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-dependencies)
* [How do I edit and validate blueprint templates?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-editing)
* [Why do blueprints get the error 'Length for variable variable name greater than the given length'?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-length)
* [Why do blueprint operations require a blueprint ID?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-install)
* [What URL format is used for referencing blueprint templates and input files?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-url)
* [How is resource provisioning performed?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-resource)
* [How do you view the blueprint provisioned resources in your cloud account?]
Canada (Toronto) ca-tor https://ca-tor.iaas.cloud.ibm.com https://ca-tor.private.iaas.cloud.ibm.com 



The Madrid region only supports dedicated host profiles with instance storage. For more information, see [Dedicated host profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profiles&interface=ui).

LinuxONE (s390x processor architecture) profiles are supported on virtual server instances in the Japan (Tokyo), Brazil (São Paulo), Canada (Toronto), and United Kingdom (London) regions.

After resources are created and accessible in your VPC, you're ready to run workloads. From inside the VPC infrastructure, you can access two types of IBM Cloud endpoints: platform as a service (PaaS) endpoints, also known as service endpoints, and infrastructure as a service (IaaS) endpoints.

Although the addresses for these endpoints look as if they communicate through the public internet, traffic to and from these endpoints does not leave IBM Cloud. Therefore, this traffic avoids the bandwidth charges associated with traffic that exits the cloud and goes onto the public internet.



 Service endpoints 

Use service endpoints to securely connect to IBM Cloud services over the IBM Cloud private network. These endpoints are available through DNS (Domain Name System) names in the cloud.ibm.com domain and resolve to 166.8.0.0/14 addresses.

Traffic to and from service endpoints are subject to ACL and security group rules. In other words, these mechanisms can be used in cases where you want to limit what virtual server instances use a particular service endpoint.

VPCs are automatically able to reach service endpoints. For more information about service endpoints, see [Services that support service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointuse-service-endpoint). After you provision a service as a private endpoint, ping the endpoint from your virtual server instance to verify that the endpoint is reachable.

You can also use VPN for VPC to access service endpoints.
Translating product details by using the CLI 

When you onboard software, you can translate certain details about your product by using the [IBM Cloud® CLI plug-in](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-plugin). Run the get-translations command to download the language files. Then, edit those files to include your specific translations and upload them using the upload-translations command. For more information, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).



 What product details can you translate? 

The following information about your product can be translated:



* Product name
* Short and long description
* Support process
* Media captions
* Feature titles and descriptions
* Readme file







 Downloading translation files 

Run the get-translations command to download the language .json files.

ibmcloud catalog offering get-translations -c CATALOG_NAME -o PRODUCT_NAME --languages en,de,ja



 Command options 

-c
: Specify the catalog name or ID.

-o
: Specify the product name or ID.

--zip (optional)
: Downloads the translation files as a .zip file.

--languages
: Provide a comma-separated list of languages to translate. If no languages are specified, all of them are downloaded. Valid options are de, en, es, fr, it, ja, ko, pt-BR, zh-Hans, and zh-Hant.

Edit the default values in each translation file with your specific translations for each language.







 Uploading translation files 

Run the upload-translations command to upload your translation files.

An English translation is required to upload other translations.

ibmcloud catalog offering upload-translations -c CATALOG_NAME -o PRODUCT_NAME --language-files en.json,de.json,ja.json



 Command options 

-c
: Specify the catalog name or ID.

-o
: Specify the product name or ID.
GRANT pg_monitor TO "ibm-cloud-base-user";





 Service Credential Users 

Users that you [create through the Service Credentials pane](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-connection-stringscreating-users-in-_service-credentials_) are members of ibm-cloud-base-user. They are able to log in, create users, and create databases.

When a user in a group creates a resource in a database, like a table, all users that are in the same group have access to that resource. Resources that are created by any of the users in ibm-cloud-base-user are accessible to other users in ibm-cloud-base-user, including the admin user.





 Users who are created through the CLI and the API 

Users that you create through the Cloud Databases API and the Cloud Databases CLI will also be members of ibm-cloud-base-user. They are able to log in, create users, and create databases.

When a user creates a resource in a database, like a table, all users that are in the same group have access to that resource. Resources that are created by any of the users in ibm-cloud-base-user are accessible to other users in ibm-cloud-base-user, including the admin user.

Users that are created directly from the API and CLI do not appear in Service Credentials, but you can [add them](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-connection-stringsadding-users-to-_service-credentials_) if you choose.





 The read-only user 

The ibm-cloud-base-user-ro manages privileges for users that are created to access read-only replicas. More information can be found on the [Configuring Read-only Replicas](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-read-only-replicas) page.





 Other ibm Users