---
title: "Results Forwarder"
description: ""
url: "https://docs.itrsgroup.com/docs/opsview/6.11.3/administration/distributing-functionality/results-forwarder/index.html"
---
Receives Passive results from outside of the system in 4k Blocks from a separately installed source, such as NRD or NSCA.

- Parses the result and extract the following information out of it.
   - Execution type.
   - Current state.
   - Output.
   - Timestamp.
   - Hostname.
   - Servicecheckname if type of message is service check.
- Sends a message with the above data to the results sender queue for processing.

## Dependencies

The Results-Forwarder requires access to the MessageQueue and Registry.  Please make sure these packages are installed, configured and running before attempting to start the results forwarder process.

## Installation

Refer to [Advanced Automated Installation](https://docs.itrsgroup.com/docs/opsview/6.11.3/install/advanced-installation/index.html).

## Configuration

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

The following options can be set:

- `results_fifo`: Location of the results FIFO. Default is `/opt/opsview/var/results.sock`.
- `resultssender_queue`: The message-queue configuration to send results.
- `registry`: Connection configuration for the Registry.
- `logging`: Component logging configuration.

## Submitting results

Results and acknowledgements can be submitted into Opsview Monitor by writing into the `/opt/opsview/var/results.sock` pipe file.  This can be used for submitting passive checks.

Entries should be written in the following format:

```
[<timestamp>] PROCESS_SERVICE_CHECK_RESULT;<host_name>;<service_name>;<return_code>;<plugin_output>
[<timestamp>] PROCESS_HOST_CHECK_RESULT;<host_name>;<return_code>;<plugin_output>
[<timestamp>] ACKNOWLEDGE_HOST_PROBLEM;<host_name>;<sticky>;<notify>;<persistent>;<author>;<comment>
[<timestamp>] ACKNOWLEDGE_SVC_PROBLEM;<host_name>;<service_name>;<sticky>;<notify>;<persistent>;<author>;<comment>
```


**Note**


The timestamp should be in epoch format.



For example, to submit a passive result that has just occurred, with a WARNING state (1) and the output text "example text" to a Service "serviceA" on Host "host1":

```
echo "[$(date +'%s')] PROCESS_SERVICE_CHECK_RESULT;host1;serviceA;1;example text" >> /opt/opsview/var/results.sock
```

Unknown hosts or services will be logged into syslog.

## Management

### Configuration

#### DPKGs

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. The package managed config files are as follows

```
/opt/opsview/watchdog/etc/services/opsview-resultsforwarder.conf
```

#### RPMs

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.

```
opt/opsview/watchdog/etc/services/opsview-resultsforwarder.conf
```

### Service administration

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

```
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-resultsforwarder
```


