Event page

Home > Using > Standard User Interface > Pages > Event page

---

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. 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 agent controller.
Last Occurred	This is the last time that an event was received that matched the event parameters. It is the latest "First Occurred" date of the last event that was received.
ITIL Component	The ITIL component that the event relates to: Availability, Capacity, Performance or Security.
Custom event properties	Custom event properties appear at the bottom of the standard event properties. These are properties that are specific to the event. 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

Any actions that have been run that are associated with this event appear here.

2.4 Previous Events

This tab contains the previous events and duplicates that are associated with the event.

2.4.1 Duplicates

Any duplicate events that have been received since the event was first opened appear here.

2.4.2 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.

1. The time the event was first opened
2. Severity increases and decreases
3. Notifications that were sent to users
4. Action results
5. The closure time