1 Overview
The events page shows you the event and its properties. Events have many different properties that are able to be used in different ways
2 Event tabs
| Event tabs
|
|---|
| Tab
|
Description
|
| Overview
|
This tab contains the event properties and event
|
| Comments
|
An annotation that a user writes and is associated with the event. Can be viewed either on the Comment or Audit tab of the event.
|
| Action results
|
This shows the results of an action that has been run while the event was open.
|
| Notifications
|
Any notifications that have taken place will be visible on the Notifications tab.
|
| Previous Events
|
Two things are shown on this tab.
- A duplicate is an event that has the same event properties as the original and therefore is classified as a duplicate. It will appear as a increment of the duplicate count as a date/time field.
- A Previous Event is an event that has been previously closed
|
| Audit log
|
The Audit log
|
2.1 Overview
| Event properties
|
|---|
| Property
|
Description
|
| ID
|
A GUID that distinguishes all of the messages. Primarily used to tell similar events apart.
|
| Severity
|
Standard categorisation based on the significance of an event:
- Information - The event does not require any immediate action and does not represent an exception.
- Warning - The event is generated when an application is approaching a threshold. Warnings are intended to notify you in order for you to take the necessary actions to prevent an exception occurring.
- Exception - This mean that the application is impacted and presents a failure, performance degradation or loss of functionality (web server down, database stopped responding, etc).
|
| Status
|
The state of event being either open or closed.
|
| Node
|
The name of the node where the event was received.
|
| First Occurred
|
The date/time that the event was detected by the management application.
| Type
|
First occurred
| | Policy
|
The time that the Veloopti agent detected the event
| | Logfile
|
The date/time that appears in the logfile. If this does not exist then it is the date/time that the Veloopti agent performed the logfile scan.
| | SNMP Trap
|
The date/time that appears in the SNMP trap
| | API
|
The date/time that is sent through the API. If this does not exist then it is the date/time that the Veloopti agent received the API event.
|
|
| Received
|
The date/time that the event was received by the Veloopti data aggregator.
|
| Last Occurred
|
The latest "First Occurred" date. If this is not the same as the First Occurred date then there will be event duplicates.
|
| ITIL Component
|
The ITIL component that the event relates to: Availability, Capacity or Security.
|
| Custom event properties
|
Custom event properties appear at the bottom of the standard event properties. This can be things like: eventID for windows event logs; URL for URL monitor policy; or anything for an inbound API policy.
|
2.3 Actions
2.4 Previous Events
2.5 Audit Log