copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2020-10-09 |
activity tracker, LogDNA, event, security, events, AT, activity tracker events, MDM, Master Data Management, IBM Cloud, IBM Cloud Pak for Data as a Service, IBM Cloud Pak for Data, |
mdm-oc |
{:external: target="_blank" .external} {:shortdesc: .shortdesc} {:table: .aria-labeledby="caption"} {:codeblock: .codeblock} {:tip: .tip} {:important: .important} {:note: .note}
{: #at_events}
As a security officer, auditor, or manager, you can use the Activity Tracker service to track how users and applications interact with the {{site.data.keyword.mdm-oc_full}} service in {{site.data.keyword.cloud}}. {: shortdesc}
{{site.data.keyword.at_full_notm}} records user-initiated activities that change the state of a service in {{site.data.keyword.cloud_notm}}. You can use this service to investigate abnormal activity and critical actions and to comply with regulatory audit requirements. In addition, you can be alerted about actions as they happen. The events that are collected comply with the Cloud Auditing Data Federation (CADF) standard. For more information, see the getting started tutorial for {{site.data.keyword.at_full_notm}}.
{: #at_actions}
The following table lists the {{site.data.keyword.at_full_notm}} actions that generate events.
Action | Triggered when someone... |
---|---|
mdm-oc.data.read | Performs read access operations on the Data microservice. |
mdm-oc.data.write | Performs write access operations on the Data microservice. |
mdm-oc.data.manage | Performs manage operations on the Data microservice. |
mdm-oc.matching.read | Performs read access operations on the Matching microservice. |
mdm-oc.matching.write | Performs write access operations on the Matching microservice. |
mdm-oc.matching.manage | Performs manage access operations on the Matching microservice. |
mdm-oc.model.read | Performs read access operations on the Model microservice. |
mdm-oc.model.write | Performs write access operations on the Model microservice. |
mdm-oc.model.manage | Performs manage operations on the Model microservice. |
mdm-oc.configurator.read | Performs read access operations on the Configuration microservice. |
mdm-oc.configurator.manage | Performs manage operations on the Configuration microservice. |
mdm-oc.pairs-analysis.read | Performs read access operations on the Pair Analysis microservice. |
mdm-oc.pairs-analysis.write | Performs read access operations on the Pair Analysis microservice. |
mdm-oc.job.read | Performs read access operations on the Jobs microservice. |
mdm-oc.job.write | Performs write access operations on the Jobs microservice. |
mdm-oc.matching.datasteward | Performs data steward access operations on the Job Analysis microservice. |
{: caption="Table 1. Actions that generate events" caption-side="top"} |
{: #at_ui}
Events that are generated by an instance of the {{site.data.keyword.at_full_notm}} service are automatically forwarded to the {{site.data.keyword.at_full_notm}} service instance that is available in the same location.
{{site.data.keyword.at_full_notm}} can have only one instance per location. To view events, you must access the web UI of the {{site.data.keyword.at_full_notm}} service in the same location where your service instance is available. For more information, see Launching the web UI through the IBM Cloud UI.