Difference between revisions of "Policy"
m |
m (Minor update) |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
== Overview == | == Overview == | ||
| − | A policy is | + | 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 selection to see either a list of policies or the policy groups that are contained in the application. Use the | |
| − | [[Category:Concepts]] [[Category:Policies]] | + | [[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 == | ||
| + | There are currently 14 different policy types. Each policy is targeted to monitor a different aspect of a server. | ||
| + | |||
| + | # Local monitoring | ||
| + | ## '''[[Policy:CI Metric Policy Page|CI Metric Thresholds (CPU, Memory, Disk, NIC)]]''' monitors the used space and free space for a file system | ||
| + | ## '''[[Policy:Windows Performance Library Policy Page|Windows performance library]]''' inspects the Windows Performance Library and returns the result | ||
| + | ## '''[[Policy:Port Availability Policy Page|Port availability]]''' watches the local host for the availability of a port | ||
| + | ## '''[[Policy:Process Performance Policy Page|Process performance]]''' watches a local process for key metrics | ||
| + | ## '''[[Policy:Service Status Policy Page|Service status]]''' watches a local service for service state changes | ||
| + | ## '''[[Policy:Log File Policy Page|Log file]]''' watches a log file for text matches or file size | ||
| + | ## '''[[Policy:Command_Execution_Policy_Page|Command execution policy]]''' runs an executable or script on a server and returns the result | ||
| + | ## '''[[Policy:Event Policy Page|Event]]''' intercepts an event sent using veloopti-event.exe on the agent | ||
| + | # Remote monitoring | ||
| + | ## '''[[Policy:Port Availability Policy Page|Port availability]]''' watches a remote host for the availability of a port | ||
| + | ## '''[[Policy:HTTP Response Policy Page|HTTP response]]''' monitors a webpage for key performance metrics | ||
| + | ## '''[[Policy:Ping Response Policy Page|Ping response]]''' ping a host and inspect the return results | ||
| + | ## '''[[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 == | ||
| + | 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. | ||
| + | |||
| + | 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. | ||
| + | |||
| + | [[Category:Concepts]] [[Category:Policies]] [[Category:Groups]] | ||
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
Policies are created and edited in an application. A policy is represented in Veloopti by the policy icon 
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).
2 Policy types
There are currently 14 different policy types. Each policy is targeted to monitor a different aspect of a server.
- Local monitoring
- CI Metric Thresholds (CPU, Memory, Disk, NIC) monitors the used space and free space for a file system
- Windows performance library inspects the Windows Performance Library and returns the result
- Port availability watches the local host for the availability of a port
- Process performance watches a local process for key metrics
- Service status watches a local service for service state changes
- Log file watches a log file for text matches or file size
- Command execution policy runs an executable or script on a server and returns the result
- Event intercepts an event sent using veloopti-event.exe on the agent
- Remote monitoring
- Port availability watches a remote host for the availability of a port
- HTTP response monitors a webpage for key performance metrics
- Ping response ping a host and inspect the return results
- SNMP policy polls a SNMP device
- SNMP Trap recipient inspects a received SNMP trap
- Agent monitoring
- 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.