1,774
edits
Changes
[[Welcome_to_Veloopti_help|Home]] > [[:Category:Using|Using]] > [[:Category:Standard_User_Interface|Standard User Interface]] > [[:Category:Pages|Pages]] > [[Action page|Action page]]
----
== Overview ==
An action is a command that can be remotely run on a node that has a Veloopti agent installed on it. Actions come in three levels of permissions: Operator; Power User; ''and'' Administrator.
=== Permissions ===
There are three levels of permissions in Actions.
;Operator
: Operator level actions require the lowest level of permissions to be run.
;Power User
: Power User level actions require more permissions than Operator level and lower than Administrator level actions. Users that can run Power User level actions can also run Operator level actions.
;Administrator
: Administrator level actions require the highest level of permissions. Users that are able to run Administrator level actions can also run Power User and Operator actions.
=== Where actions can be run ===
Actions can be run in two different locations: on servers and through an event.
==== Actions on servers ====
Actions can be run directly on a server that has a Veloopti agent. When clicking on the server name in either the main node page, or the node page in an application; there is a item named Actions where they can be run.
==== Actions on events ====
Actions can also be run from an Event. <more here>
== Action tabs ==
{| class="wikitable" style="text-align: left;"
!colspan="6"|Action tabs
|-
|'''Tab'''
|'''Description'''
|-
|[[Action_page#Overview_2|Overview]]
|This tab contains the main overview of the Action
|-
|[[Action_page#Attributes|Attributes]]
|The attributes of the action are the commands and parameters that are run on the node.
|-
|[[Action_page#History|History]]
|This shows the results of an action that has been run while the event was open.
|-
|[[Action_page#Audit_Log|Audit log]]
|The Audit log
|-
|}
=== Overview ===
'''Name'''
The name of the policy is used to reference it from different places in Veloopti. An action needs to have a unique name in the [[Application|Application]] that it is in.
'''Description'''
The description is where you enter some text that describes what the action does.
'''Type'''
The action type is currently limited to a command type action. More of these will be released in the future.
'''Level'''
There are three levels of actions in Veloopti: Operator; Power User and Administrator. Each level is able to be run by users who are members of a role that have the appropriate permission assigned to it.
=== Attributes ===
{| class="wikitable" style="text-align: left;"
!colspan="6"|Event properties
|-
|'''Property'''
|'''Description'''
|-
|ID
|A [[Glossary_of_acronyms#G|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|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|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|node]] where the event was received.
|-
|First Occurred
|The date/time that the event was detected by the management application.
{| class="wikitable" style="text-align: left;"
|'''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|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 [[Glossary_of_acronyms#I|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.
|-
|}
=== Attributes ===
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.
=== History ===
Any actions that have been run that are associated with this event appear here.
=== 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
[[Category:Pages]] [[Category:Actions]]
----
== Overview ==
An action is a command that can be remotely run on a node that has a Veloopti agent installed on it. Actions come in three levels of permissions: Operator; Power User; ''and'' Administrator.
=== Permissions ===
There are three levels of permissions in Actions.
;Operator
: Operator level actions require the lowest level of permissions to be run.
;Power User
: Power User level actions require more permissions than Operator level and lower than Administrator level actions. Users that can run Power User level actions can also run Operator level actions.
;Administrator
: Administrator level actions require the highest level of permissions. Users that are able to run Administrator level actions can also run Power User and Operator actions.
=== Where actions can be run ===
Actions can be run in two different locations: on servers and through an event.
==== Actions on servers ====
Actions can be run directly on a server that has a Veloopti agent. When clicking on the server name in either the main node page, or the node page in an application; there is a item named Actions where they can be run.
==== Actions on events ====
Actions can also be run from an Event. <more here>
== Action tabs ==
{| class="wikitable" style="text-align: left;"
!colspan="6"|Action tabs
|-
|'''Tab'''
|'''Description'''
|-
|[[Action_page#Overview_2|Overview]]
|This tab contains the main overview of the Action
|-
|[[Action_page#Attributes|Attributes]]
|The attributes of the action are the commands and parameters that are run on the node.
|-
|[[Action_page#History|History]]
|This shows the results of an action that has been run while the event was open.
|-
|[[Action_page#Audit_Log|Audit log]]
|The Audit log
|-
|}
=== Overview ===
'''Name'''
The name of the policy is used to reference it from different places in Veloopti. An action needs to have a unique name in the [[Application|Application]] that it is in.
'''Description'''
The description is where you enter some text that describes what the action does.
'''Type'''
The action type is currently limited to a command type action. More of these will be released in the future.
'''Level'''
There are three levels of actions in Veloopti: Operator; Power User and Administrator. Each level is able to be run by users who are members of a role that have the appropriate permission assigned to it.
=== Attributes ===
{| class="wikitable" style="text-align: left;"
!colspan="6"|Event properties
|-
|'''Property'''
|'''Description'''
|-
|ID
|A [[Glossary_of_acronyms#G|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|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|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|node]] where the event was received.
|-
|First Occurred
|The date/time that the event was detected by the management application.
{| class="wikitable" style="text-align: left;"
|'''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|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 [[Glossary_of_acronyms#I|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.
|-
|}
=== Attributes ===
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.
=== History ===
Any actions that have been run that are associated with this event appear here.
=== 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
[[Category:Pages]] [[Category:Actions]]