1,774
edits
Changes
Initial page
[[Welcome_to_Veloopti_help|Home]] > [[:Category:Using|Using]] > [[:Category:Web_User_Interface|Web User Interface]] > [[:Category:Views|Views]] > [[Policy:Port_Availability_Policy_Page|Port avauilability]]
----
== Overview ==
The Port availability policy will connect to a remote port and determine whether ???
A policy is an instructions run on one or more of your monitored servers looking for an event that could lead to loss of, or disruption to, an organisation's operations, services or functions. Each policy is found in an application
A [[policy|policy]] is represented in Veloopti by the policy icon: <sup>[[file:icon_policy.png|30px]]</sup>
Port availability policies must be added to a [[Group|Policy Group]] for automated deployment onto one or more managed nodes.
=== Creating or editing a policy ===
[[File:Port availability page.png|thumb|350px|The Port availability policy page is found by selecting a policy from the policy view.]]
Port availability policies are created and edited from within an [[Application|application]]. A policy is only visible from within the application that it was created in. After entering an application select 'Policies' from the application breadcrumb to view the list of policies that are available in the application.
# Click on the Application menu item
# Click on the Application
# Select the Policies breadcrumb as shown below to view the [[Policy_view|Policy view]]
# From here you can either click on the [[Policy_Wizard|Policy Wizard]] to create a new Policy or select a ping Response policy to modify it.
[[File:Breadcrumb application policy.png|500px]]
== Navigating the policy page ==
Tabs run down the left hand side of the view. Clicking on a tab will change the page that allows for a particular part of the policy to be modified.
They are: [[Policy:Ping_Response_Policy_Page#Overview_2|Overview]], [[Policy:Port_Availability_Policy_Page#Attributes|Attributes]], [[Policy:Port_Availability_Policy_Page#Conditions|Conditions]], [[Policy:Port_Availability_Policy_Page#Node_Overrides|Node Overrides]], [[Policy:Port_Availability_Policy_Page#Schedule|Schedule]], [[Policy:Port_Availability_Policy_Page#Audit_Log|Audit Log]] and [[Policy:Port_Availability_Policy_Page#View_Data|View Data]].
=== Port Availability Policy Page ===
'''NAME'''
The title of the policy that can be used to tell the policy apart from others
'''DESCRIPTION'''
Describes the policy and explains what it does
'''TYPE'''
Port Availability
'''NODE OVERRIDES CONDITIONS'''
Enabling this slider makes the Node Overrides tab visible.
=== Attributes ===
'''Host'''
The full DNS name or IP address that will have the port availability tested on
'''Port'''
The TCP port number that will be tested
'''Timeout'''
Timeout in milliseconds to wait for a valid response from the Host.
=== Conditions ===
Either add a new row by clicking on the [Add] button or click on an existing row to enter the edit condition dialogue box.
The rules may be moved up and down by selecting and holding the rule to change its position.
Click on the [Add] button to bring up the dialogue to add a condition to the policy.
NOTE: Currently changing the position of order of the rules does not do anything as they are evaluated in order of severity.
::'''EVALUATE'''
:::'''Metric''' Select a metric upon which to perform a threshold evaluation. The options available are:
::::Timed out
:::'''Operator'''Select an operator to perform against the Metric above. Different options are available for different metrics.
::::Equals
:::'''Value''' Enter a value to compare the metric against using the operator.
::::Yes
::::No
::'''BREACH AND RESET'''
:::'''Breach duration''' Enter the number of consecutive breaches that need to occur for an event to be raised. Note this is breaches for a policy run, not individual ping failures.
:::'''Reset Duration''' Enter the number of consecutive successful policy runs, the number that the metric must be (usually) below, for the event severity to be set to Normal. Note this for successful policy nuns, not successful individual pings.
::'''CREATE EVENT'''
::'''Event Severity''' The severity that appears on the event that is raised by a threshold violation of the rule
::'''Event Short Description''' The short event description that appears on the event that is raised
::'''Event Long Description''' The long description that appears in the event
::'''Auto Action''' Select an action to run automatically when the condition of raising an event is met. These are [[Action|actions]] that have been created for the Application.
::'''Close event if auto action runs successfully''' This check box closes the event if the command exits with a successful 'error code'. For instance, the ping command on a Mac returns an error code of 0 for success and 2 for a ping failure. And the ping command on a windows OS in a command prompt returns 0 for success and 1 for failure.
:::On Windows, after running the command, run the below command to see the error code that the command exited with
::: <pre style="color: silver; background: black;">C:\users\Muuss\echo %ERRORLEVEL%</pre>
::'''EVENT ACTIONS''' These actions are available to be run by any user that has the "Run Action from Event" permission. Unlike normal actions it does not rely on the Action "Level" permission of Operator, Power User or Administrator
::'''HELP TEXT''' This text appears on the event in the "Help" section.
::'''NOTIFICATION WORKFLOW''' Select the Notification Workflow that will be used for notifications and escalations.
=== Node Overrides ===
One policy can run on multiple nodes using the same conditions to create events. Individual nodes may require different threshold values in these conditions for effective monitoring. This is known as a "Node override condition".
This is currently not enabled.
=== Schedule ===
'''TYPE'''
::'''Basic''' Run the policy once per minute or once per hour
::'''Time of day''' Run the policy once her day
::'''Custom''' Run the policy on a complex schedule
'''EVERY'''
::'''Basic''' Select "Minutes" or "Hours" and type when on the minute or hour the policy should run.
::'''Time of day''' Select hour and minute and the weekday(s) that the policy should run.
::'''Custom''' Select "Minutes" or "Hours" and type when on the minute or hour the policy should run. Select the time range when the policy should be active: e.g. 9:00am - 5:00pm. Select the weekday(s) that the policy should run.
=== Audit Log ===
'''DATE/TIME''' The date/time that the audit event occurred
'''USER''' The user that initiated the audited event
'''EVENT''' A description of what happened to the policy. Blue text indicates that it is a link to the described item.
'''ACTION''' If an action is available for the audit item it can be initiated here. For instance, roll back the policy to the previous version or restore the accidentally deleted policy.
=== View Data ===
'''SELECT YOUR NODE''' Use the drop down list box to select the node that it is deployed to. Graphs will then be visible in the below space that contains the metrics that have been collected over the last hour.
NOTE: Only nodes with this policy currently deployed are able to be selected.
[[Category:Views]] [[Category:Policies]]
----
== Overview ==
The Port availability policy will connect to a remote port and determine whether ???
A policy is an instructions run on one or more of your monitored servers looking for an event that could lead to loss of, or disruption to, an organisation's operations, services or functions. Each policy is found in an application
A [[policy|policy]] is represented in Veloopti by the policy icon: <sup>[[file:icon_policy.png|30px]]</sup>
Port availability policies must be added to a [[Group|Policy Group]] for automated deployment onto one or more managed nodes.
=== Creating or editing a policy ===
[[File:Port availability page.png|thumb|350px|The Port availability policy page is found by selecting a policy from the policy view.]]
Port availability policies are created and edited from within an [[Application|application]]. A policy is only visible from within the application that it was created in. After entering an application select 'Policies' from the application breadcrumb to view the list of policies that are available in the application.
# Click on the Application menu item
# Click on the Application
# Select the Policies breadcrumb as shown below to view the [[Policy_view|Policy view]]
# From here you can either click on the [[Policy_Wizard|Policy Wizard]] to create a new Policy or select a ping Response policy to modify it.
[[File:Breadcrumb application policy.png|500px]]
== Navigating the policy page ==
Tabs run down the left hand side of the view. Clicking on a tab will change the page that allows for a particular part of the policy to be modified.
They are: [[Policy:Ping_Response_Policy_Page#Overview_2|Overview]], [[Policy:Port_Availability_Policy_Page#Attributes|Attributes]], [[Policy:Port_Availability_Policy_Page#Conditions|Conditions]], [[Policy:Port_Availability_Policy_Page#Node_Overrides|Node Overrides]], [[Policy:Port_Availability_Policy_Page#Schedule|Schedule]], [[Policy:Port_Availability_Policy_Page#Audit_Log|Audit Log]] and [[Policy:Port_Availability_Policy_Page#View_Data|View Data]].
=== Port Availability Policy Page ===
'''NAME'''
The title of the policy that can be used to tell the policy apart from others
'''DESCRIPTION'''
Describes the policy and explains what it does
'''TYPE'''
Port Availability
'''NODE OVERRIDES CONDITIONS'''
Enabling this slider makes the Node Overrides tab visible.
=== Attributes ===
'''Host'''
The full DNS name or IP address that will have the port availability tested on
'''Port'''
The TCP port number that will be tested
'''Timeout'''
Timeout in milliseconds to wait for a valid response from the Host.
=== Conditions ===
Either add a new row by clicking on the [Add] button or click on an existing row to enter the edit condition dialogue box.
The rules may be moved up and down by selecting and holding the rule to change its position.
Click on the [Add] button to bring up the dialogue to add a condition to the policy.
NOTE: Currently changing the position of order of the rules does not do anything as they are evaluated in order of severity.
::'''EVALUATE'''
:::'''Metric''' Select a metric upon which to perform a threshold evaluation. The options available are:
::::Timed out
:::'''Operator'''Select an operator to perform against the Metric above. Different options are available for different metrics.
::::Equals
:::'''Value''' Enter a value to compare the metric against using the operator.
::::Yes
::::No
::'''BREACH AND RESET'''
:::'''Breach duration''' Enter the number of consecutive breaches that need to occur for an event to be raised. Note this is breaches for a policy run, not individual ping failures.
:::'''Reset Duration''' Enter the number of consecutive successful policy runs, the number that the metric must be (usually) below, for the event severity to be set to Normal. Note this for successful policy nuns, not successful individual pings.
::'''CREATE EVENT'''
::'''Event Severity''' The severity that appears on the event that is raised by a threshold violation of the rule
::'''Event Short Description''' The short event description that appears on the event that is raised
::'''Event Long Description''' The long description that appears in the event
::'''Auto Action''' Select an action to run automatically when the condition of raising an event is met. These are [[Action|actions]] that have been created for the Application.
::'''Close event if auto action runs successfully''' This check box closes the event if the command exits with a successful 'error code'. For instance, the ping command on a Mac returns an error code of 0 for success and 2 for a ping failure. And the ping command on a windows OS in a command prompt returns 0 for success and 1 for failure.
:::On Windows, after running the command, run the below command to see the error code that the command exited with
::: <pre style="color: silver; background: black;">C:\users\Muuss\echo %ERRORLEVEL%</pre>
::'''EVENT ACTIONS''' These actions are available to be run by any user that has the "Run Action from Event" permission. Unlike normal actions it does not rely on the Action "Level" permission of Operator, Power User or Administrator
::'''HELP TEXT''' This text appears on the event in the "Help" section.
::'''NOTIFICATION WORKFLOW''' Select the Notification Workflow that will be used for notifications and escalations.
=== Node Overrides ===
One policy can run on multiple nodes using the same conditions to create events. Individual nodes may require different threshold values in these conditions for effective monitoring. This is known as a "Node override condition".
This is currently not enabled.
=== Schedule ===
'''TYPE'''
::'''Basic''' Run the policy once per minute or once per hour
::'''Time of day''' Run the policy once her day
::'''Custom''' Run the policy on a complex schedule
'''EVERY'''
::'''Basic''' Select "Minutes" or "Hours" and type when on the minute or hour the policy should run.
::'''Time of day''' Select hour and minute and the weekday(s) that the policy should run.
::'''Custom''' Select "Minutes" or "Hours" and type when on the minute or hour the policy should run. Select the time range when the policy should be active: e.g. 9:00am - 5:00pm. Select the weekday(s) that the policy should run.
=== Audit Log ===
'''DATE/TIME''' The date/time that the audit event occurred
'''USER''' The user that initiated the audited event
'''EVENT''' A description of what happened to the policy. Blue text indicates that it is a link to the described item.
'''ACTION''' If an action is available for the audit item it can be initiated here. For instance, roll back the policy to the previous version or restore the accidentally deleted policy.
=== View Data ===
'''SELECT YOUR NODE''' Use the drop down list box to select the node that it is deployed to. Graphs will then be visible in the below space that contains the metrics that have been collected over the last hour.
NOTE: Only nodes with this policy currently deployed are able to be selected.
[[Category:Views]] [[Category:Policies]]