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.
The Executor requires access to the MessageQueue. Please make sure we have the message queue *
Refer to Advanced Automated Installation.
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.
- input_queue: The message-queue configuration to receive execution messages.
- file_sync_queue: The message-queue configuration to receive receive file-sync requests.
- output_queue: The message-queue configuration to send back results. Note: this is just a place-holder and should not be modified, as the actual name of the results queue is dynamic.
- registry: Connection configuration for the Registry.
- logging: Component logging configuration. Change "NOTICE" to "DEBUG" to turn on debugging. Logs will go to /var/log/syslog or /var/log/messages
- service_check: The time in seconds that a service check is allowed to run before it is forcibly killed.
- host_check: The time in seconds that a host check is allowed to run before it is forcibly killed.
- event_handler: The time in seconds that an event handler is allowed to run before it is forcibly killed.
- send_notifications: The time in seconds that a notification script is allowed to run before it is forcibly killed.
- instant_command: The time in seconds for other types of general executions to run before they are forcibly killed.
execution_timeouts configuration default is defined as follows:
executor: execution_timeouts: service_check: 60 host_check: 60 event_handler: 60 send_notifications: 60 instant_command: 60
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.
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.
Watchdog configuration is in:
As root, start, stop and restart the service using:
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-executor
Updated almost 4 years ago