Difference between revisions of "Event page"

From Veloopti Help
Jump to: navigation, search
m
m
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
[[Welcome_to_Veloopti|Home]] > [[:Category:Using|Using]] > [[:Category:Standard_User_Interface|Standard User Interface]] > [[:Category:Pages|Pages]] > [[Event page|Event page]]
+
[[Welcome_to_Veloopti_help|Home]] > [[:Category:Using|Using]] > [[:Category:Web_User_Interface|Web User Interface]] > [[:Category:Pages|Pages]] > [[Event page|Event page]]
 
----
 
----
  
  
 
== Overview ==
 
== Overview ==
−
An event is opened by clicking on its description on the [https://ap1.veloopti.com.au/events events view] web page which is found on the main menu. The pages are not protected so not everyone is able to see them.
+
An event is opened by clicking on an event description on the [https://ap1.veloopti.com.au/events 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.
  
 
== Event tabs ==
 
== Event tabs ==
Line 33: Line 33:
 
|}
 
|}
  
−
=== Overview ===
+
=== [Overview] ===
  
 
{| class="wikitable" style="text-align: left;"
 
{| class="wikitable" style="text-align: left;"
Line 42: Line 42:
 
|-
 
|-
 
|ID
 
|ID
−
|A [[Glossary_of_acronyms#G|GUID]] that distinguishes all of the messages.  Primarily used to tell similar events apart.
+
|A [[Glossary_of_acronyms#G|GUID]] that distinguishes all of the messages.  Used by Veloopti to distinguish all events.
 +
|-
 +
|Path
 +
|The [[Path|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
 
|Severity
Line 63: Line 66:
 
|-
 
|-
 
|Policy
 
|Policy
−
|The time that the Veloopti agent detected the event
+
|The date/time that the event was first detected on a Veloopti Agent
 
|-
 
|-
 
|Logfile
 
|Logfile
Line 76: Line 79:
 
|}
 
|}
 
|-
 
|-
−
|Received
+
|First Received
−
|The date/time that the event was received by the Veloopti [[Agent_controller|agent controller]].
+
|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
 
|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.
+
|This is the "First Occurred" date/time of either the original event, or of the latest duplicate received.  
 
|-
 
|-
 
|ITIL Component
 
|ITIL Component
−
|The [[Glossary_of_acronyms#I|ITIL]] component that the event relates to: Availability, Capacity, Performance or Security.
+
|When an event is detected it is classified into one of five ways that are [[Glossary_of_acronyms#I|ITIL]] aligned: Availability; Performance; Capacity; Security ''and'' Configuration.
 
|-
 
|-
 
|Custom event properties
 
|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.
+
|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.
 
|-
 
|-
 
|}
 
|}
  
−
=== Comments ===
+
=== [Comments] ===
  
 
Type in the section that say "Add a new comment" and click on the [[file:Add comment.png|70px]] button to add your comments to the event.
 
Type in the section that say "Add a new comment" and click on the [[file:Add comment.png|70px]] button to add your comments to the event.
  
−
=== Actions ===
+
=== [Actions] ===
 +
 
 +
'''Select an Option'''
 
Any actions that have been run that are associated with this event appear here.
 
Any actions that have been run that are associated with this event appear here.
  
−
=== Previous Events ===
+
'''Return Code: - Duration:'''
 +
 
 +
'''Results:'''
 +
 
 +
==== [Duplicates] ====
 +
Any duplicate events that have been received since the event was first opened appear here.
 +
 
 +
 
 +
=== [Previous Events] ===
 
This tab contains the previous events and duplicates that are associated with the event.
 
This tab contains the previous events and duplicates that are associated with the event.
  
−
==== Duplicates ====
 
−
Any duplicate events that have been received since the event was first opened appear here.
 
  
 
==== Previous Events ====
 
==== Previous Events ====

Latest revision as of 20:06, 26 September 2019

Home > Using > Web 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.
  1. 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.
  2. 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. 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:
  • 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 date/time that the event was first detected on a Veloopti Agent
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.
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 Add comment.png 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.

  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
Retrieved from "http://help.veloopti.com.au/index.php?title=Event_page&oldid=4849"