Configuring Dynamic Thresholds

Exporting data to Obcerv Copied

Your Opsview Cloud instance must first be configured by ITRS Support to export data to, and import data from, Obcerv.

Configure Service Checks Copied

Dynamic Thresholds are configured on a per-host-service basis. You can enable or disable Dynamic Thresholds for service checks through the Opsview Configuration > Dynamic Thresholds page.

This page is only visible to users with the ADMINACCESS permission. See the section Adding a New Role for more information. Additionally, the Dynamics Threshold configuration page will only show Host-Services the current Opsview user has access to.

When you first access the Dynamic Thresholds configuration page, you will not see any service checks listed. No host-services are enabled for Dynamic Thresholds by default.

1. To enable Dynamic Threshold for a service check or multiple service checks, use the search bar to find the desired services. Pressing ENTER will display a list of matching services in the table.

   

2. Select the service checks you want to enable Dynamic Thresholds for by clicking the checkbox, then click Apply threshold changes. To disable Dynamic Thresholds for a service, uncheck the box and click Apply threshold changes again.

   

3. Once enabled, the service check will be listed in the table. The Current Thresholds column displays the latest threshold data for the service check (or Awaiting Data if no data has been imported yet).

   

Limitations Copied

• Dynamic Thresholds are only available for service checks that return a single metric value.
• Dynamic Thresholds currently only support service checks that calculate thresholds as VALUE > THRESHOLD_VALUE. Less-than thresholds are not supported.
• Dynamic Thresholds only support service checks that include the Dynamic Thresholds macros: $WARNINGGT or $CRITICALGT as values for warning and critical threshold arguments.
  • Currently only a subset of the bundled Service Checks support Dynamic Thresholds.
  • Dynamic Threshold macros are written in the format $WARNINGGT:DEFAULTVALUE$, where DEFAULTVALUE is the default threshold value if Dynamic Thresholds are not available/not configured.
• Threshold prediction accuracy will improve based on the length of time data has been exported to Obcerv. While one week of exported data is recommended before using Dynamic Thresholds, optimal accuracy is achieved with up to four weeks of data.
  • For newly exported host-service metric data, Dynamic Thresholds may not be available for a brief period until sufficient data is collected.

Troubleshooting Copied

Dynamic Thresholds configuration page is missing Copied

The Dynamic Thresholds configuration page may not be accessible in the navigation bar if the Dynamic Thresholds feature is not included in your Opsview license.

Please contact ITRS Support for more information.

Host-services are missing in the Dynamic Thresholds search Copied

Host-services must be compatible with the Dynamic Thresholds feature to appear in the configuration page search results. Compatibility is determined by the following criteria:

• Host-service must be returning performance metrics.
• Service check definition must contain one of the Dynamic Thresholds macros: $WARNINGGT or $CRITICALGT.

My enabled host-services are in an Awaiting Data state Copied

If a host-service’s dynamic threshold configuration is showing Awaiting Data, it’s possible that service metric data isn’t reaching Obcerv. Verify that the correct host-services are being exported through the Obcerv Web Console and check Opsview log files for any related errors.