Tracking shared events
BMC Client Management administrators can track all events that are shared with other software products via the Alerts and Events node. All events that are available for external integration are part of the Alert & Event event log model.
This view provides the following selection options which can be combined for the display. When opened the table of this node is empty. To launch the display click Find :
Select from this list the type of event log model for which to display the logged events, for this case you always need to select the Alert & Event option.
Select in this field the status value for which the logged events are to be displayed.
Select in this field the date from which on the logged events are to be displayed.
Select in this field the date up to which the logged events are to be displayed.
The table displays the following information for all alerts and events that are shared and tracked with other applications.
Alert & Event
The Alert & Event model logs agent operation events, such as events and alerts generated by operational rules, by the inventory module, security alerts, and so on. It shows the following information for each event:
This column is not displayed under the Alerts and Events of a device.
The date and time the alert occurred in the default time format.
An event is closed either automatically by the BMC Client Management master, because an automatic solution was applied and the agent found the device to be now compliant. If this automatic solution is not possible the alert can only be closed manually from the target application after it was manually resolved.
Defines the severity of the selected alert, Error, Information or Warning.
Defines the type of event that is being logged.
The alert sub-category to which the alert/event was assigned. This value can be freely defined by the administrator.
Displays the textual description of the alert/event.
Indicates if this alert is shared with other applications such as BMC Remedyforce, BMC FootPrints Service Core, or Remedy with Smart IT via the external integration. It only appears after the ticket was actually created in the target integration.
The name of the administrator who acknowledged the event.
Last Modified By
Displays the name of either the last person that last modified the object or its contents, such as the administrator, or it may be the system that last executed any modifications.
This free text field can contain additional information concerning the selected object.
Filtering alerts and events
This view always only shows the alerts and events logged for a specific event log model. To display the events and alerts of another model or to further limit the displayed list to those of a specific status or timeframe, proceed as follows:
Select the desired event log model from the Model Name drop-down box.
To filter for a specific status of the current model do not modify this selection.
- You can further filter the alerts and events of the selected model according to the following criteria:
- Select a specific status value from the Status drop-down box to display only alerts/events of a specific status type.
To filter for events of a specific timeframe select the start and end date of the desired timeframe in the calendar boxes.
You can use only one criteria for filtering or you can use a combination of them.
- Click Find .
The table will refresh and display only those alerts/events that comply with the selected criteria.
After you access the Alerts and Events node the alert icon in the status bar disappears. However the status of the alerts themselves has not yet changed. To acknowledge specific alerts, proceed as follows:
- Mark the alerts to be acknowledged in the table in the right window pane.
- Select Edit > Acknowledge Alerts
A confirmation windowdisplays. .
- Select Yes to confirm and proceed with the action.
The status of the selected alerts will now be changed from
Unnotified Alerts to
Acknowledged Alerts .
Purging alerts and events
Alerts and events can be purged. Be careful when using this operation, ALL alerts and events of this event log model for the current device/device group will be irrevocably deleted from the database.
- Click Purge .
A confirmation window appears.
- Click Yes to confirm.
Another confirmation window appears if one or more of the selected alerts/events has a connected incident ticket in BMC Remedyforce, BMC FootPrints Service Core, or Remedy with Smart IT.
- If the incident tickets that were created in BMC Remedyforce should be closed at the same time click Yes , otherwise click No.
All alerts and events will be deleted from the database and, if requested, the status of the connected incident ticket(s) in BMC Remedyforce, BMC FootPrints Service Core, or Remedy with Smart IT will be changed to
Deleting individual alerts and events
It is possible to delete individual alerts and events that are no longer required.
- Select the alert(s)/event(s) to delete in the table to the right.
- Click Edit > Delete
A confirmation window appears. .
- Click Yes to confirm.
Another confirmation window appears if one or more of the selected alerts/events has a connected incident ticket in BMC Remedyforce .
- If the incident tickets that were created in BMC Remedyforce should be closed at the same time click Yes , otherwise click No .
All selected alerts and events will be deleted from the database and, if requested, the status of the connected incident ticket(s) in BMC Remedyforce will be changed to