## Description
_Opsview Results Exporter_ exports results to services such as Splunk, syslog, local files and arbitrary HTTP endpoints.
## Known Issues
When logging data to Rsyslog via TCP, only the first message has the correct priority; subsequent messages use the `user.notice` priority.
## Installation
Next, ensure that your component configuration (see Configuration section below) contains the correct **MessageQueue encoder key**, **password**, and **Registry password**. These will be the values set when deploying your Opsview system, as specified in `/opt/opsview/deploy/etc/user_secrets.yml`.
## Configuration
The opsview-results-exporter component ships with a default configuration file (`/opt/opsview/resultsexporter/etc/resultsexporter.defaults.yaml`). Any changes to this file will be overwritten on package updates so you should not edit this file if you want to keep your changes across package updates.
Create `/opt/opsview/resultsexporter/etc/resultsexporter.yaml` for any custom settings if it does not already exist. `resultsexporter.yaml` is not overwritten across package updates and overrides settings in `resultsexporter.defaults.yaml`.
resultsexporter.yaml permissions
Ensure `
/opt/opsview/resultsexporter/etc/resultsexporter.yaml` is accessible by the opsview group with read permissions.**E.g**
Example contents of `/opt/opsview/resultsexporter/etc/`:
The following options can be overridden in `resultsexporter.yaml`:
results_queue: The message queue configuration.
outputs: The list of outputs to export results to, currently results can be exported via syslog, file and HTTP.
registry: The connection configuration for the registry.
default_fields: The default message fields to export. See [Field Mapping](🔗).
default_filter: The default filter that is applied to messages. See [Filtering](🔗).
Ensure that your component configuration contains the correct **MessageQueue encoder key**, **password**, and **Registry password**. These values are set when deploying your Opsview system, as specified in `/opt/opsview/deploy/etc/user_secrets.yml`.
When overriding settings in `resultsexporter.yaml`, refer to the structure used in `resultsexporter.defaults.yaml`. For example, to override the messagequeue/registry settings within `resultsexporter.yaml`:
Refer to the examples as described on [Exporting Results](🔗) for how to add your own outputs. **Please ensure the passwords used match that within your /opt/opsview/deploy/etc/user_secrets.yml found on your deployment server**
## 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:
#### 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.
### Service Administration
As root, start, stop and restart the service using:
## Troubleshooting
### Credentials
If you receive this error message, with the /var/log/opsview/opsview. please check the /opt/opsview/resultsexporter/etc/resultsexporter.yaml contains the correct password for the registry. The opsview-resultsexporter will need to be restarted if any change is made.
### Configuration File Formatting
If you receive this error message, with the /var/log/opsview/opsview. please check the /opt/opsview/resultsexporter/etc/resultsexporter.yaml filter syntax is correct. For the error below, an extra parenthesis was present. The opsview-resultsexporter will need to be restarted if any change is made.