Extend Service Check Timeout
To do this, please follow the below:
-
Identify if your service check in question is running on one or more collector servers Navigate to your UI and navigate to “Configuration > System > Monitoring Collectors”, then under the Collectors tab find your collector in question under the column “Collector” within the “Registered Collectors” section.
-
On the right-hand side of this row will be the “Monitoring Clusters” column that will show you the cluster names for your collectors; filter this column on the collector name shown here to see if one or more collectors are within your cluster of interest
-
If more than one collector is in the cluster, you will need to perform this change on all of them
-
File to edit
/opt/opsview/executor/etc/executor.yaml
-
Change to make
- add the lines shown at the bottom of these steps
-
Restart the opsview-executor and the opsview-agent on the same collector(s) where the change has been made
/opt/opsview/watchdog/bin/opsview-monit restart opsview-executor systemctl restart opsview-agent -
Apply Changes within your Opsview UI
-
Troubleshoot the service check respectively
Lines to add:
- please remember that the indentation is necessary and must be exact
- the indentation is two spaces on the
execution_timeoutsline and four space characters on theservice_checkline
- the indentation is two spaces on the
execution_timeouts:
service_check: 120
If you would like to make these changes permanent, perform a global override of this config as below:
vim /opt/opsview/deploy/etc/user_vars.yml
And add the below lines to the user_vars file, think of this file as a place to hard-code your configuration:
service_check: 120
## Increase the timeouts for various execution steps from the default of 60 seconds
opsview_executor_config:
execution_timeouts:
service_check: 120
service_check_slow: 240
host_check: 120
event_handler: 90
send_notifications: 75
instant_command: 120
Further Information: Extending-opsview-agent