ITRS Opsview Cloud Documentation


The Executor receives execution messages from the Scheduler and uses them to execute service-check plugins, then return the results to the Scheduler.

It runs on multiple sub-processes to maximise the throughput of execution.

Dependencies Copied

The Executor requires access to the MessageQueue. Please make sure you have the message queue.

Installation Copied

Refer to Advanced Automated Installation.

Configuration Copied

The user configuration options should be set in /opt/opsview/executor/etc/executor.yaml. Default values are shown in /opt/opsview/executor/etc/executor.defaults.yaml, but changes should not be made here since the file will get overwritten on package update.

The below list shows the options that can be set. Note that any changes made to the component configuration file will be overwritten when opsview-deploy is next run.

The execution_timeouts configuration default is defined as follows:

    service_check: 60
    service_check_slow: 120
    host_check: 30
    event_handler: 60
    send_notifications: 60
    instant_command: 30

Management Copied

Configuration Copied

DPKGs Copied

Watchdog service files are now managed by the package; doing a remove would leave the watchdog service file behind with a .save extension. Purging the package will remove it.

RPMs Copied

Watchdog service files are now managed by the package. Any modifications will be saved at upgrade and remove processes with the .rpmnew and .rpmsave extensions correspondingly.

Service Administration Copied

Watchdog configuration is in: /opt/opsview/watchdog/etc/services/opsview-executor.conf.

As root, start, stop and restart the service using:

/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-executor
["Opsview On-premises"] ["User Guide"]

Was this topic helpful?