Policy

From Veloopti Help
Revision as of 19:48, 24 November 2021 by Nigel (talk | contribs) (Update order)
Jump to: navigation, search

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. Windows performance library inspects the Windows Performance Library and returns the result
    2. Port availability watches the local or a remote host for the availability of a port
    3. Process performance watches a local process for key metrics
    4. Service status watches a local service for service state changes
    5. CI Metric Thresholds (CPU, Memory, Disk, NIC) monitors the used space and free space for a file system
    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. HTTP response monitors a webpage for key performance metrics
    2. Ping response ping a host and inspect the return results
    3. SNMP policy polls a SNMP device
    4. 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.