Event page
Home > Using > Web User Interface > Pages > Event page
Contents
1 Overview
An event is opened by clicking on an event description on the events view web page. This page is found second to the left on the main menu. An event is able to be viewed if you have the appropriate permissions to the application that contains the event.
2 Event tabs
Event tabs | |||||
---|---|---|---|---|---|
Tab | Description | ||||
Overview | This tab contains the event properties and event | ||||
Comments | Any annotation that a user writes and is associated with the event. Can be viewed either on the comment or audit tab of the event. | ||||
Actions | This shows the results of an action that has been run while the event was open. | ||||
Previous Events | Two things are shown on this tab.
| ||||
Audit log | The Audit log |
2.1 [Overview]
Event properties | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Property | Description | ||||||||||
ID | A GUID that distinguishes all of the messages. Used by Veloopti to distinguish all events. | ||||||||||
Path | The path is what is used to correlate events of a similar nature together. When there is an open event that contains the same path as new event, instead of there being two events the second one will be duplicated against the first. | ||||||||||
Severity | Standard categorisation based on the significance of an event:
| ||||||||||
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.
| ||||||||||
First Received | The date/time that the event was received by Veloopti. This field can be helpful in determining the length of time that it takes for the event to get to Veloopti. It can also be helpful to assist to determine whether there was a delay in receiving the event from the agent. | ||||||||||
Last Occurred | This is the "First Occurred" date/time of either the original event, or of the latest duplicate received. | ||||||||||
ITIL Component | When an event is detected it is classified into one of five ways that are ITIL aligned: Availability; Performance; Capacity; Security and Configuration. | ||||||||||
Custom event properties | Some policies can send event properties specific to the policy type through to Veloopti. These properties will be listed in the even at this point. This can be things like: eventID for windows event logs; URL for URL monitor policy; or anything for an inbound API policy. |
2.2 [Comments]
Type in the section that say "Add a new comment" and click on the button to add your comments to the event.
2.3 [Actions]
Select an Option Any actions that have been run that are associated with this event appear here.
Return Code: - Duration:
Results:
2.3.1 [Duplicates]
Any duplicate events that have been received since the event was first opened appear here.
2.4 [Previous Events]
This tab contains the previous events and duplicates that are associated with the event.
2.4.1 Previous Events
This contains the previous events that occurred that are of a similar nature to the event being viewed.
Occurred: The last time either the event or a duplicate of the event was received. Click on the link to take you directly to this event.
Node: The node name that the event occurred on.
Closing Comment: This contains the closing comment if one was entered at the time of closing it.
Number of comments: This contains the total number of comments for the event.
2.5 Audit Log
This tab contains the audit log for the event. Anything that occurs in relation to the event occurs here.
- The time the event was first opened
- Severity increases and decreases
- Notifications that were sent to users
- Action results
- The closure time