Configuring Dynamic Thresholds

Exporting data to ITRS Analytics Copied

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

Configure service checks Copied

The Dynamic Thresholds page is only visible to users with ADMINACCESS permission, and it only displays host-services the current Opsview user has access to. For more information, see Adding a New Role.

Watch the following product tour to learn how to enable Dynamic Thresholds, verify plugin arguments, and test that your service checks are properly configured.

Note

When the service check runs, the $WARNINGDT;DEFAULTVALUE;HARDLIMIT$ and $CRITICALDT;DEFAULTVALUE;HARDLIMIT$ macros are replaced with the current threshold values if Dynamic Thresholds has been correctly configured. If Dynamic Thresholds is not configured properly or applied to the check, the default value will be used; the value is never allowed to exceed the hard limit.

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: $WARNINGDT or $CRITICALDT 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 $WARNINGDT;DEFAULTVALUE$, where DEFAULTVALUE is the default threshold value if Dynamic Thresholds are not available/not configured.
  • Optionally, you can also set a hard limit for Dynamic Threshold macros. This is defined as $WARNINGDT;DEFAULTVALUE;HARDLIMIT$, where HARDLIMIT will cap any calculated dynamic thresholds at its value. Note that hard limits only apply to checks with Dynamic Thresholds enabled and do not affect default values.
• Threshold prediction accuracy will improve based on the length of time data has been exported to ITRS Analytics. 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

Data is not being exported to ITRS Analytics Copied

This can occur for a variety of reasons, which includes the following:

• Misconfiguration of the Results Exporter component
• A certificate update on the ITRS Analytics system after the Results Exporter was configured
• Invalid data within the messages being processed

Please contact ITRS Support for assistance in investigating.

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: $WARNINGDT or $CRITICALDT.

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 ITRS Analytics. Verify that the correct host-services are being exported through the ITRS Analytics Web Console and check Opsview log files for any related errors.