copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2021-09-09 |
activity tracker for {{site.data.keyword.iae_full_notm}}, {{site.data.keyword.la_short}} for {{site.data.keyword.iae_full_notm}}, {{site.data.keyword.iae_full_notm}} events, {{site.data.keyword.iae_full_notm}} security, audit logs for {{site.data.keyword.iae_full_notm}}, viewing {{site.data.keyword.iae_full_notm}} events, {{site.data.keyword.iae_full_notm}} events |
AnalyticsEngine |
{:new_window: target="_blank"} {:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:pre: .pre}
{: #at_events-serverless}
As a security officer, auditor, or manager, you can use the {{site.data.keyword.at_short}} service to track how users and applications interact with {{site.data.keyword.iae_full_notm}} in {{site.data.keyword.cloud}}.
{{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.
The following table lists the actions that generate an event:
{: #at_actions}
Action | Description |
---|---|
ibmanalyticsengine.instance.read |
Retrieve the details of an instance |
ibmanalyticsengine.instance.update |
Update the configuration of the instance after instance creation |
ibmanalyticsengine.instance-logging.create |
Create the logging configuration for an instance |
ibmanalyticsengine.instance-logging.update |
Update the logging configuration of an instance |
ibmanalyticsengine.instance-logging.read |
Retrieve the logging configuration details of an instance |
ibmanalyticsengine.instance-logging.delete |
Delete the logging configuration of an instance |
ibmanalyticsengine.application.create |
Deploy a Spark application |
ibmanalyticsengine.application.read |
Retrieve the details of the submitted Spark application including the state and configuration settings |
ibmanalyticsengine.application.delete |
Delete a Spark application request or a running Spark application |
ibmanalyticsengine.livybatch.create |
Create a Spark application through the Livy batch interface |
ibmanalyticsengine.livybatch.read |
Retrieve the details of a Livy batch application, including the state |
ibmanalyticsengine.livybatch.delete |
Delete a Livy application request or a running Livy batch application |
ibmanalyticsengine.historyserver.start |
Start the Spark history server of an instance |
ibmanalyticsengine.historyserver.stop |
Stop the Spark history server of an instance |
ibmanalyticsengine.historyserver.read |
Retrieve the details of the Spark history server of an instance |
{: caption="Actions that generate management events" caption-side="top"} |
{: #at-viewing-events}
Events that are generated by an instance of the {{site.data.keyword.iae_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{: new_window}.