Difference between revisions of "Policy"

From Veloopti Help
Jump to: navigation, search
m
m (Minor update)
 
(12 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
== Overview ==
 
== Overview ==
  
−
Policies are created and edited in an [[application|application]]. A policy is instructions for the monitoring of something from a computer. Policies are deployed to a node using [[group|groups]].  
+
A policy is an instructions for the monitoring of a server for an event that could lead to loss of, or disruption to, an organisation's operations, services or functions. The server should have a Veloopti agent running on it. Policies are deployed to a server that then run on a predefined schedule. This can be anything from once per minute to once per year.
  
−
After entering an [[application|application]] use the [[Breadcrumbs|breadcrumb navigator]] to select the policies option to see the [[Policies_view|policies view]]
+
After entering an [[application|application]] use the [[Breadcrumbs|breadcrumb navigator]] to select the policies selection to see either a list of policies or the policy groups that are contained in the application. Use the  
  
 
[[file:breadcrums_config_policy.png|350px]]
 
[[file:breadcrums_config_policy.png|350px]]
 +
 +
Policies are created and edited in an [[application|application]]. A policy is represented in Veloopti by the policy icon <sup>[[file:icon_policy.png|40px]]</sup>
 +
 +
A policy is unique to an application and may only be deployed to servers that reside in the application. In order for a policy to be deployed it must be inside a policy group and the policy group must then be linked to a node group that contains the node(s).
 +
 +
[[file:pic_node_group_and_policy_group.png|400px]]
 +
 +
  
 
== Policy types ==
 
== Policy types ==
 
There are currently 14 different policy types. Each policy is targeted to monitor a different aspect of a server.
 
There are currently 14 different policy types. Each policy is targeted to monitor a different aspect of a server.
  
−
# '''[[Command execution policy|Command execution]]''' Runs a executable or script on a server and returns the result
+
# Local monitoring
−
# '''[[Disk Filesystem policy|Disk / Filesystem]]''' Montor the used space and free space for a file system
+
## '''[[Policy:CI Metric Policy Page|CI Metric Thresholds (CPU, Memory, Disk, NIC)]]''' monitors the used space and free space for a file system
−
# '''[[Event policy|Event]]''' Intercept an event sent from the event program and inspect it for enhancements
+
## '''[[Policy:Windows Performance Library Policy Page|Windows performance library]]''' inspects the Windows Performance Library and returns the result
−
# '''[[HTTP response policy|HTTP response]]''' Monitor a webpage for key performance metrics
+
## '''[[Policy:Port Availability Policy Page|Port availability]]''' watches the local host for the availability of a port
−
# '''[[Log file policy|Log file]]''' Watches a log file for text matches or file size
+
## '''[[Policy:Process Performance Policy Page|Process performance]]''' watches a local process for key metrics
−
# '''[[Ping response policy|Ping response]]''' Ping a host and inspect the return results
+
## '''[[Policy:Service Status Policy Page|Service status]]''' watches a local service for service state changes
−
# '''[[Port availability policy|Port availability]]''' Watch the local or a remote host for the availability of a port
+
## '''[[Policy:Log File Policy Page|Log file]]''' watches a log file for text matches or file size
−
# '''[[Process performance policy|Process performance]]''' Watch a local process for key metrics
+
## '''[[Policy:Command_Execution_Policy_Page|Command execution policy]]''' runs an executable or script on a server and returns the result
−
# '''[[Service status policy|Service status]]''' Watch a local service for service state changes
+
## '''[[Policy:Event Policy Page|Event]]''' intercepts an event sent using veloopti-event.exe on the agent
−
# '''[[SNMP Poll policy|SNMP policy]]''' Poll a SNMP device
+
# Remote monitoring
−
# '''[[SNMP Trap receipt policy|SNMP Trap recipient]]''' Inspect a received SNMP trap
+
## '''[[Policy:Port Availability Policy Page|Port availability]]''' watches a remote host for the availability of a port
−
# '''[[Veloopti Agent Health policy|Veloopti agent health]]''' Watch a Veloopti agent to see whether it is connected or not
+
## '''[[Policy:HTTP Response Policy Page|HTTP response]]''' monitors a webpage for key performance metrics
−
# '''[[Windows Performance Library policy|Windows performance library]]''' Inspect the Windows Performance Library
+
## '''[[Policy:Ping Response Policy Page|Ping response]]''' ping a host and inspect the return results
−
# '''[[CI Metric Thresholds policy|CI Metric thresholds]]''' Inspect the global metrics that are being collected for the node
+
## '''[[Policy:SNMP Poll Policy Page|SNMP policy]]''' polls a SNMP device
 +
## '''[[Policy:SNMP Trap Receipt Policy Page|SNMP Trap recipient]]''' inspects a received SNMP trap
 +
# Agent monitoring
 +
## '''[[Policy:Veloopti Agent Health Policy Page|Veloopti agent health]]''' monitors a Veloopti agent to see whether it is connected or not
  
 
== Deploying a policy to a server ==
 
== Deploying a policy to a server ==
−
Policies are deployed to a server by adding it to a policy group. The policy group must also be linked to a node group that contains the server that the policy is to be deployed to.
+
Policies are deployed to a server by adding it to a policy [[Group|group]]. The policy group must also be linked to a node group that contains the server that the policy is to be deployed to.
  
 
One or more policies can be added to a policy group. A policy in a policy group is a member of the group. In order for the policies in the policy group to be deployed to the nodes in a node group the policy group must be linked to the node group. A policy group can be linked to one or more node groups. All nodes in the node group that have a policy group linked to it can have the policies deployed to them.
 
One or more policies can be added to a policy group. A policy in a policy group is a member of the group. In order for the policies in the policy group to be deployed to the nodes in a node group the policy group must be linked to the node group. A policy group can be linked to one or more node groups. All nodes in the node group that have a policy group linked to it can have the policies deployed to them.

Latest revision as of 19:18, 29 November 2021

Home > An Overview > Concepts > Policy

1 Overview

A policy is an instructions for the monitoring of a server for an event that could lead to loss of, or disruption to, an organisation's operations, services or functions. The server should have a Veloopti agent running on it. Policies are deployed to a server that then run on a predefined schedule. This can be anything from once per minute to once per year.

After entering an application use the breadcrumb navigator to select the policies selection to see either a list of policies or the policy groups that are contained in the application. Use the

Breadcrums config policy.png

Policies are created and edited in an application. A policy is represented in Veloopti by the policy icon Icon policy.png

A policy is unique to an application and may only be deployed to servers that reside in the application. In order for a policy to be deployed it must be inside a policy group and the policy group must then be linked to a node group that contains the node(s).

Pic node group and policy group.png


2 Policy types

There are currently 14 different policy types. Each policy is targeted to monitor a different aspect of a server.

  1. Local monitoring
    1. CI Metric Thresholds (CPU, Memory, Disk, NIC) monitors the used space and free space for a file system
    2. Windows performance library inspects the Windows Performance Library and returns the result
    3. Port availability watches the local host for the availability of a port
    4. Process performance watches a local process for key metrics
    5. Service status watches a local service for service state changes
    6. Log file watches a log file for text matches or file size
    7. Command execution policy runs an executable or script on a server and returns the result
    8. Event intercepts an event sent using veloopti-event.exe on the agent
  2. Remote monitoring
    1. Port availability watches a remote host for the availability of a port
    2. HTTP response monitors a webpage for key performance metrics
    3. Ping response ping a host and inspect the return results
    4. SNMP policy polls a SNMP device
    5. SNMP Trap recipient inspects a received SNMP trap
  3. Agent monitoring
    1. Veloopti agent health monitors a Veloopti agent to see whether it is connected or not

3 Deploying a policy to a server

Policies are deployed to a server by adding it to a policy group. The policy group must also be linked to a node group that contains the server that the policy is to be deployed to.

One or more policies can be added to a policy group. A policy in a policy group is a member of the group. In order for the policies in the policy group to be deployed to the nodes in a node group the policy group must be linked to the node group. A policy group can be linked to one or more node groups. All nodes in the node group that have a policy group linked to it can have the policies deployed to them.

A policy group is located in an application and is not able to be linked to a node group outside of the application. A policy cannot be directly deployed to a node.

Retrieved from "http://help.veloopti.com.au/index.php?title=Policy&oldid=5661"