GuidesREST APISlack CommunitySupport PortalOpsview 6.8+ Documentation
Hey! These docs are for version 6.4, which is no longer officially supported. Click here for the latest version, 6.7!

## Description

This package provides means for opsview web to get netflow and sflow data for viewing the UI via the dashboard. It processes netflow and sflow data and pushes messages on the message queues to be stored in the database via `results-flow`. The various dashlets send a command via the Orchestrator API to the relevant Collector where the netflow data is being stored to get Top 10 Host and Port, Transmitters and Receivers information. Results flow stores data which dashlets use to show sources summary and sources history.

## Dependencies

  • opsview-flow-base

  • opsview-messagequeue

Please make sure `opsview-messagequeue` is installed configured and running before attempting to run the flowcollector.

On the Orchestrator server please make sure you install` opsview-results-flow` package. This package reads the data sent from flow collector and adds into the database to be shown in the dashboards.

## Installation

To install Flow Collector, you need to edit /opt/opsview/deploy/etc/user_vars.yml file and append the following:


Then, run the following command as root:

## Configuration
##### Flow collector
No configuration is required if the flow-collector is installed on the same machine as the orchestrator and messagequeue. In any other setup the collector needs to know where the opsview-messagequeue is installed. Flow collector will then determine the correct flow-results queue, flow-request and flow-response queue. There are two possible scenarios here;
  1. The user edits the component yaml file path `/opt/opsview/flowcollector/etc/flowcollector.yaml` (on the collector) and edits `/opt/opsview/resultsflow/etc/resultsflow.yaml` (on the orchestrator)  to point to the correct messagequeue as below.
  2. The user edits the loadbalancer messagequeue.cfg to point to the correct message queue server. Examples of which are further below.
##### Flow Collector

##### Results flow

##### Load Balancer

## Management
### Configuration
#### DPKGs
Watchdog service configuration 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. Any modifications to the files will be saved at upgrade and removal of the package.
  • /opt/opsview/watchdog/etc/services/opsview-flowcollector.conf
  • /opt/opsview/watchdog/etc/services/opsview-resultsflow.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-flowcollector.conf.
  • /opt/opsview/watchdog/etc/services/opsview-resultsflow.conf.
### Service Administration
As root, start, stop and restart the service using: