| copyright |
|
||
|---|---|---|---|
| lastupdated | 2025-04-10 | ||
| keywords | |||
| subcollection | atracker |
{{site.data.keyword.attribute-definition-list}}
{: #overview}
Learn how to configure your account to manage auditing events by using {{site.data.keyword.atracker_full}}. You can use {{site.data.keyword.atracker_short}} to collect auditing events that are generated by services in your {{site.data.keyword.cloud_notm}} account. The events comply with the Cloud Auditing Data Federation (CADF) standard. {: shortdesc}
{: caption="The {{site.data.keyword.atracker_short}} service" caption-side="bottom"}
You can use {{site.data.keyword.atracker_short}}, a platform service, to manage auditing events at the account-level by configuring targets and routes that define where auditing data is routed. {{site.data.keyword.atracker_short}} can only route events that are generated in supported regions.
The following table outlines the locations where you can configure {{site.data.keyword.atracker_short}} to collect and manage auditing events:
See locations for the locations where you can configure {{site.data.keyword.atracker_short}} to collect and manage auditing events.
You can use {{site.data.keyword.atracker_short}} to manage events from enabled-services in the account. To see the list of services that generate events that you can manage by using {{site.data.keyword.atracker_short}}, see Services generating events.
{: #overview-1}
To configure {{site.data.keyword.atracker_short}} in your account, you must define which locations auditing events are collected from and where are they routed and stored. You must configure 1 or more targets, and 1 or more routes. You must also configure the account settings.
-
A target defines a resource where you can collect auditing events. For more information, see Targets.
-
A route defines the rules that determine the targets where auditing events are routed to in your account. For more information, see Routes.
-
The account settings configuration defines information such as default targets where events are collected in the account, types of endpoints that are allowed to manage the configuration, and allowed locations to store the data in the account. For more information, see Account configuration settings.
For each account, you can choose the regions where auditing events are collected.
You can only configure regions where {{site.data.keyword.atracker_short}} is supported. See Locations. {: important}