Audit message changes
Message change auditing makes it possible to audit changes made to messages. As a user in a regulated environment, it is important to you to be able to audit which changes to messages were made, when messages were changed, and by whom.
Message change auditing provides auditing capability for the following message changes:
- Message state change (such as own, disown, acknowledge, unacknowledge)
- Message severity change
- Message text change
- Message annotation change
- Message download using DB Maintenance (only a single audit message is written, not a message change event for every downloaded/deleted message)
- Custom message attribute change
Message change auditing does not audit the following message changes:
- New message creation or forwarded message arriving
- Message action state change (such as running, successful, failed)
- Message counter change
NOTE:Action Execution ("Action started by user .." and "Action execution cancelled by user ..") itself is audited as part of the message and action server auditing. It is not necessary to audit the action state changes to messages that were caused by action execution.
Audit message changes for forwarded messages
Server-based flexible management allows you to forward messages between two management servers (HPOM for Windows and HPOM for UNIX), and also to forward message operations (such as acknowledge, own, and severity change) for forwarded messages. This means that messages are kept in sync between the management servers even when a message is changed on one of the servers.It is possible to configure auditing for forwarded message changes independently of the auditing for local message changes. As with auditing for local message changes, auditing for forwarded messages is turned off by default. To get auditing for forwarded messages, you must enable it manually, in addition to enabling auditing for local message changes.
Audit DB maintenance
The DB Maintenance functionality of HPOM downloads acknowledged messages at specified times and deletes them from the database. This is a change to messages that need to be audited. However, because this is a mass update that may concern lots of messages, not every change to a message should be audited.So for DB Maintenance, just one message change audit event is generated that explains how many messages have been touched by DB Maintenance.
For more information on DB Maintenance, see the help topics DB Maintenance Component details and Change StartTime DBMaint and DBMaintTimeSpec Settings.
Related Topics: