Skip to content

Latest commit

 

History

History
83 lines (60 loc) · 4.45 KB

bm-activity-tracker-events.md

File metadata and controls

83 lines (60 loc) · 4.45 KB
copyright lastupdated keywords subcollection
years
2016, 2019
2018-11-06
activity tracker, bare metal, {{site.data.keyword.Bluemix}}
bare-metal

{:new_window: target="_blank"} {:shortdesc: .shortdesc} {:screen: .screen} {:pre: .pre} {:table: .aria-labeledby="caption"} {:codeblock: .codeblock} {:tip: .tip} {:download: .download}

Activity Tracker events

{: #bm-at-events}

As a security officer, auditor, or manager, you can use the {{site.data.keyword.cloudaccesstrailfull}} service to track how users and applications interact with bare metal servers in {{site.data.keyword.Bluemix}}. The account owner and users that are linked with the account can trigger bare metal server events that are logged in {{site.data.keyword.cloudaccesstrailshort}}. {:shortdesc}

The {{site.data.keyword.cloudaccesstrailshort}} service records user-initiated activities that change the state of a service in {{site.data.keyword.Bluemix_notm}}. For more information, see About {{site.data.keyword.cloudaccesstrailshort}}.

To get started monitoring your user's actions,see Getting started with The IBM Cloud Activity Tracker.

An initiator can be a user, a service, or an application. For a user to generate events, the user must have access to Infrastructure resources in {{site.data.keyword.Bluemix}} console. {: tip}

Bare metal server instance events

{: #bare-metal-events}

You can audit a bare metal server through its life cycle by using the {{site.data.keyword.cloudaccesstrailshort}} service.

The following table lists the actions that generate an event:

Action Description
audit-log.bare-metal.provision An event is generated when an initiator provisions a bare metal server.
audit-log.bare-metal-port.disable An event is generated when an initiator disables a port in a bare metal server.
audit-log.bare-metal-port.enable An event is generated when an initiator enables a port in a bare metal server.
audit-log.bare-metal-port-speed.update An event is generated when an initiator updates the port speed in a bare metal server.
audit-log.bare-metal.power-off An event is generated when an initiator powers off a bare metal server.
audit-log.bare-metal.reboot An event is generated when an initiator reboots a bare metal server.
audit-log.bare-metal.soft-reboot An event is generated when an initiator does a soft reboot on a bare metal server.
audit-log.bare-metal.hard-reboot An event is generated when an initiator does a hard reboot on a bare metal server.
audit-log.bare-metal.power-on An event is generated when an initiator powers on a bare metal server.
audit-log.bare-metal.rename An event is generated when an initiator renames a bare metal server.
audit-log.bare-metal.rescue An event is generated when an initiator rescues a bare metal server.
audit-log.bare-metal.reload An event is generated when an initiator performs an operating system (OS) reload for a bare metal server.
{: caption="Table 2. Bare metal actions" caption-side="top"}

Viewing events

{: #bm-view-events}

The {{site.data.keyword.cloudaccesstrailshort}} events are available in the {{site.data.keyword.cloudaccesstrailshort}} account domain that is available in the {{site.data.keyword.Bluemix_notm}} region where the events are generated. For more information, see Viewing account events.

{{site.data.keyword.cloudaccesstrailshort}} events are automatically forwarded to the {{site.data.keyword.cloudaccesstrailshort}} service in the same region where the action happens.