vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Using the Track Access template 

Use the IBM Cloud Activity Tracker Track Access template to gain insight on your IBM Cloud access requests. Monitor login requests, unauthorize access, and denied requests.



 Overview 

The Activity Tracker track access template includes the following artifacts:



* Parsing templates to pull additional information from the data to enhance searchability and simplify customization such as region, RC and accountID.
* Views and screens that allow you to monitor activity in your account.



This template uses global events that are available through the Frankfurt region. In Activity Tracker, you can monitor global events through the instance in Frankfurt (EU-DE). Deploy this template in the Frankfurt region to monitor activity.





 Deploying the track access templates 

Complete the following steps to deploy the track access template objects in 1 Activity Tracker instance:



 Step 1. Launch the template library 

The Activity Tracker hosted event search offering template library offers multiple tiles that group predefined views, dashboards, and screens by area. One of them is the Track Archiving template.

Complete the following steps to launch the Activity Tracker template library:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud dashboard opens.
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/icon_hamburger.svg) > Observability.
3. Select Activity Tracker.

The list of Activity Tracker instances is displayed.

There is 1 instance per region.
4. Select the Activity Tracker instance in the region where you want to deploy the template. Then, click Open Dashboard.







 Step 2. Install the template 

Complete the following steps to deploy the Track Access template:



1. From the Activity Tracker instance UI, click the Settings icon !
See [Installing the Activity Tracker Event Routing CLI](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-cli-config&interface=cli).
* You need a user ID that is a member, or an owner of, an IBM Cloud account. To get an IBM Cloud user ID, go to: [Create an account](https://cloud.ibm.com/login).
* Every user that manages the Activity Tracker Event Routing configuration in your account must be assigned an access policy. The policy determines what actions the user can perform. The allowable actions are customized and defined by Activity Tracker Event Routing as operations that are allowed to be performed on the service. The actions are then mapped to IAM user roles. [Learn more](https://cloud.ibm.com/docs/atracker?topic=atracker-iam).

Your user ID needs administrator platform permissions to manage the IBM Cloud Activity Tracker Event Routing service. Contact the account owner. The account owner can grant another user access to the account for the purposes of managing user access, and managing account resources. [Learn more](https://cloud.ibm.com/docs/account?topic=account-userroles).







 Step 1: Configure a Event Streams topic 

Auditing events that are collected in your account can be routed to an Event Streams topic.

When you configure Activity Tracker Event Routing, you can define a target per region. The target defines the Event Streams instance and topic where auditing events in that region are routed.

Complete the following steps:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).
2. Create an Event Streams instance.

Check the limitations of the Event Streams service plans. For more information, see [Limits and quotas](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-kafka_quotas).

a.
If you have a JIRA project and want to connect to it, for the JIRA type, click Existing:

a. Type the JIRA project key for the JIRA project. You can find the project key in the JIRA project's URL.

b. Type the base API URL for your JIRA instance. You can find the API URL from the header of your JIRA instance. Click the Administration icon and click System.

c. If you are connecting to a private JIRA instance, or you want to receive traceability information from a public JIRA instance, enter your JIRA user name and password.

d. To track the deployment of code changes for the project by creating labels and comments for referenced issues, select the Track deployment of code changes checkbox. Make sure that you use JIRA Smart Commit to reference the JIRA issues in your GitHub commits. If you don't select this option, the JIRA tool integration ignores any commits.
4. If you want to create a JIRA project, for the JIRA type, click New:

a. Type a JIRA project key to use for the new project. This key is used as a unique identifier in the project URL.

b. Type a name for the JIRA project.

c. Type the base API URL for your JIRA instance. You can find the API URL from the header of your JIRA instance. Click the Administration icon and click System.

d. Type the user name for the JIRA project lead that you want to use for this project. To specify someone as the JIRA project lead, that person must have the project lead permission in JIRA.

e. Type the administrator's user name for this instance of JIRA.

f. Type the administrator's password for this instance of JIRA.

g. To track the deployment of code changes for the project by creating labels and comments for referenced issues, select the Track deployment of code changes checkbox. Make sure that you use JIRA Smart Commit to reference the JIRA issues in your GitHub commits.
Decide whether public endpoints, private endpoints, or both are allowed to manage the Activity Tracker Event Routing account configuration.
3. Define the locations where an account administrator can define targets to collect auditing events.

You can choose any of the supported locations where Activity Tracker Event Routing is available. For more information, see [Locations](https://cloud.ibm.com/docs/atracker?topic=atracker-regions&interface=cli).

Take into account any corporate or industry compliance requirements such as Financial Services Validated locations, or EU-managed regions.
4. Define 1 or more default targets in the account that will collect auditing events from supported Activity Tracker Event Routing locations where you have not configured how you want to collect the auditing data.

If you define more than 1 target, all default targets get a copy of an auditing event that does not have a clearly defined routing rule to indicate where to collect it in the account. You can define up to 2 default targets per account.







 IAM permissions 

Users must have the following [IAM roles](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources) to manage the Activity Tracker Event Routing account settings.



Table 1. Required IAM roles to manage the Activity Tracker Event Routing account settings.

 Role Minimum scope Minimum required roles Action 

 atracker.setting.get Account Administrator <br>Editor <br>Viewer <br>Operator Get setting information 
 atracker.setting.update Account Administrator Update settings 



Users must have the following [IAM roles](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources) to migrate the account's Activity Tracker Event Routing configuration.



Table 2. Required IAM roles to migrate the Activity Tracker Event Routing account configuration.

 Role Minimum scope Minimum required roles Action 

 atracker.migration.post Account Administrator Start the migration of Activity Tracker Event Routing resources in the account. 
 atracker.migration.get Account Administrator <br>Editor <br>Viewer <br>Operator Get the status of Activity Tracker Event Routing resources that are being migrated from V1 to V2.
Read and agree to the [Direct Link prerequisites](https://cloud.ibm.com/docs/dl?topic=dl-ibm-cloud-dl-prerequisites) and review Cloud Services [Terms](https://www.ibm.com/software/sla/sladb.nsf/searchsaas/?searchview&searchorder=4&searchmax=0&query=%28Direct+Link+Connect%29). Then, click Create to complete your order.

If you want to add GB egress data to your estimate, click Add to estimate to calculate the cost. You can also click the About tab for links to Direct Link pricing tables and other helpful resources.



After you create your Direct Link order, the Direct Link dashboard indicates Create in progress order status.

If you refresh the page after a few minutes, it shows Provisioned status.





 Completing the connection 

To complete your connection, follow these steps:



1. Contact your network provider and negotiate connectivity to your on-premises or colocation.
2. Create a request on the provider portal to order a virtual circuit. Reference the case ID of the Direct Link Connect request as your Request ID or Authorization ID.
3. Configure the BGP parameters on your Edge router for BGP session establishment. After this completes, the BGP status indicates Established.







 Related link 

[Direct Link Connect service providers and locations](https://cloud.ibm.com/docs/dl?topic=dl-locationsconnect-locations)
is_bare_metal_server_network_interface](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_bare_metal_server_network_interface)<br> * [ibm_is_bare_metal_server_network_interface_floating_ip](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_bare_metal_server_network_interface_floating_ip)<br> * [ibm_is_bare_metal_server_network_interface_floating_ips](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_bare_metal_server_network_interface_floating_ips)<br> * [ibm_is_bare_metal_server_network_interface_reserved_ip](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_bare_metal_server_network_interface_reserved_ip)<br> * [ibm_is_bare_metal_
Why does the Ingress status show an ERRDSIA error? 

Virtual Private Cloud

Classic infrastructure

Satellite

You can use the the ibmcloud ks ingress status-report ignored-errors add command to add an error to the ignored-errors list. Ignored errors still appear in the output of the ibmcloud ks ingress status-report get command, but are ignored when calculating the overall Ingress Status.

 What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud ks ingress status-report get command, you see an error similar to the following example.

The subdomain has incorrect addresses registered (ERRDSIA).

 Why it’s happening 

Normally, the NLB-DNS subdomains should hold IP addresses or load balancer hostnames that are tied to one or more LoadBalancer services on your cluster, but one or more domains have unknown addresses registered.

 How to fix it 

Identify and update any NLB-DNS subdomains that have incorrect addresses registered.



1. Get the list of the managed domains using the ibmcloud ks ingress domain ls[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliingress-domain-ls).
2. Get the list of LoadBalancer services from your cluster.

kubectl get services -A | grep LoadBalancer
3. Compare the outputs of the two previous commands and identify the subdomains that have incorrect addresses registered.
4. If you no longer need a specific domain, you can use the ibmcloud ks ingress domain rm[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliingress-domain-rm) to remove it.
5. If you still need the domain, you can update the registered addresses for the domain by using the ibmcloud ks ingress domain update[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliingress-domain-update) command.