copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2025-02-24 |
activity tracker, cluster management, events, logging, openshift |
openshift |
{{site.data.keyword.attribute-definition-list}}
Include your activity tracking events file in an Observability topic group in the How to navigation group in your toc.yaml file.
{: #at_events}
{{site.data.keyword.cloud_notm}} services, such as {{site.data.keyword.openshiftlong_notm}}, generate activity tracking events. {: shortdesc}
Activity tracking events report on activities that change the state of a service in {{site.data.keyword.cloud_notm}}. You can use the events to investigate abnormal activity and critical actions and to comply with regulatory audit requirements.
You can use {{site.data.keyword.atracker_full_notm}}, a platform service, to route auditing events in your account to destinations of your choice by configuring targets and routes that define where activity tracking events are sent. For more information, see About {{site.data.keyword.atracker_full_notm}}.
You can use {{site.data.keyword.logs_full_notm}} to visualize and alert on events that are generated in your account and routed by {{site.data.keyword.atracker_full_notm}} to an {{site.data.keyword.logs_full_notm}} instance.
As of 28 March 2024, the {{site.data.keyword.at_full_notm}} service is deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to {{site.data.keyword.logs_full_notm}} before 30 March 2025. During the migration period, customers can use {{site.data.keyword.at_full_notm}} along with {{site.data.keyword.logs_full_notm}}. Activity tracking events are the same for both services. For information about migrating from {{site.data.keyword.at_full_notm}} to {{site.data.keyword.logs_full_notm}} and running the services in parallel, see migration planning. {: important}
{: #at-locations}
{{site.data.keyword.openshiftlong_notm}} activity tracking events are generated in all supported regions.
Locations where activity tracking events are sent to {{site.data.keyword.at_full_notm}} hosted event search
{: #at-legacy-locations}
{{site.data.keyword.openshiftlong_notm}} sends activity tracking events to {{site.data.keyword.at_full_notm}} hosted event search in all supported regions.
{: #atracker-locations}
{{site.data.keyword.openshiftlong_notm}} sends activity tracking events by {{site.data.keyword.atracker_full_notm}} in all supported regions.
{: #at-enable}
Activity Tracker can be enabled for your cluster during cluster create time.
- If you do not already have an instance in your account, create one.
- In the cluster create UI, configure you cluster as required.
- In the Observability integrations section, enable the Activity Tracker option. If an Activity Tracker service instance already exists in your account for the region you selected for you cluster, it is automatically connected to your cluster. If there is not an existing instance for the region, one is automatically created for you. Note that only one instance per region can exist in your account.
- Continue configuring the cluster.
{: #at-viewing}
To view events, navigate to the Observability page in the {{site.data.keyword.redhat_openshift_notm}} clusters console{: external}, then click Activity Tracker. Click on the instance you want to view events for, then click Open dashboard. A separate window appears where you can view your events.
{: #log-launch-standalone}
For information on launching the {{site.data.keyword.logs_full_notm}} UI, see Launching the UI in the {{site.data.keyword.logs_full_notm}} documentation.
{: #at_actions_platform}
For a list of all events generated by IBM Cloud Kubernetes Service, see the {{site.data.keyword.cloud_notm}} Activity Tracker events reference doc.