Submit passive results

Overview Copied

The Infrastructure Agent allows passive check results from configured plugins to be submitted into Opsview without requiring NRPE communication from the Collector to the Agent. This mechanism extends the existing polling mechanism within the Agent, enabling scheduled plugin execution and submission of results to an HTTP Receiver in the Results Forwarder.

Note

Previously, the NSCA (Nagios Service Check Acceptor) handled this functionality through the Opsview Agent, which has now reached End of Support (EOS) status.

To ensure continued support and compatibility, all new and existing monitoring must now be deployed using the Infrastructure Agent and the new mechanism for submitting passive results to Opsview.

This mechanism relies on the Opsview Results Forwarder, which hosts the HTTP Receiver responsible for accepting incoming results submitted by the Agent. When a forwarder is configured, the result is no longer sent to the cache-manager. Instead, it is submitted externally over HTTP, allowing outbound passive result submission from the Agent to Opsview.

Prerequisites Copied

This mechanism requires a properly configured Opsview Results Forwarder with an enabled HTTP Receiver. For configuration instructions, refer to the Opsview documentation on Receiving passive results via HTTP Receiver.

Configuration Copied

The following is a configuration sample to enable passive result forwarding from the Infrastructure Agent into Opsview. It must be manually added (or deployed using a preferred automation tool) to the following files:

• Windows:

C:\Program Files\Infrastructure Agent\cfg\custom\agent.yml

• Linux:

/opt/itrs/infrastructure-agent/cfg/custom/agent.yml

forwarders:

  forwarder_client_1:  # Label to refer to this forwarder
    host: <results-forwarder-host>
    port: 5667  # NSCA port
    user: <username>  # Optional user/password combo for basic auth
    password: <password>  # Optional user/password combo for basic auth
    tls_enabled: true
    tls:
      ca_cert: /opt/opsview/etc/ssl/ca.pem
      ca_path: null
      cert_file: /opt/opsview/etc/ssl/local-client.pem
      key_file: /opt/opsview/etc/ssl/local-client.pem
      check_client_cert: True
      cipher_suite: 'ECDH+AESGCM:ECDH+AES256:ECDH+AES128:!aNULL:!MD5:!DSS'
      context_options:
        - NO_SSLv3
        - NO_TLSv1
        - NO_TLSv1_1
    idle_timeout: 12  # Optional idle time before connection is closed (default 12s)
    connection_timeout: 30  # Optional (default 30s)
    network_timeout: 60  # Optional (default 60s)

poller_schedule:
  my_plugin:  # Reference to the plugin tag, in commands
    interval: 10
    forwarder: forwarder_client_1
    hostname: host1  # Optional (defaults to local hostname)
    servicecheckname: service1  # Optional (defaults to plugin tag)

commands:
  my_plugin:
    ...

Note

If a forwarder is specified in the poller_schedule, the plugin is executed as a standard plugin, but results are sent through the specified client instead of the cache-manager via the original poller mechanism, which takes the script output and sends it back into the cache-manager.