Distributing Functionality
Overview Copied
One of the key advantages of distributed functionality is that load is taken away from the main Opsview Monitor system and is shared around other servers.
It should not be necessary for the majority of organisations to do this as the Simple Automated Installation sets up all components onto one server but if you have:
- a large number of devices to monitor.
- high-demand monitoring requirements.
- a greater need for resiliency against failures.
Then you can easily move necessary components to other locations.
Opsview Monitor packages Copied
This is a list of all the available packages that comprise Opsview Monitor. For a server to perform specific functionality, only those required packages details on the sub-pages need to be installed. See also the numbers notes for some rows in this table.
| Component Name (according to Watchdog) | Alias (According to Web UI) | Distributed Status | Required |
|---|---|---|---|
| infrastructure-agent | Infrastructure Agent | Distributed | Yes |
| opsview-autodiscoverymanager | Autodiscovery Manager | Orchestrator only | Yes |
| opsview-bsm | BSM | Distributed | Yes (2) |
| opsview-datastore | DataStore | Distributed | Yes (2) |
| opsview-downtimemanager | Downtime Manager | Distributed | Yes (2) |
| opsview-executor | Executor | Distributed | Yes (2) |
| opsview-filesync | File Sync | Distributed | Yes (3) |
| opsview-freshnesschecker | Freshness Checker | Distributed | Yes (2) |
| opsview-licensemanager | License Manager | Orchestrator only | Yes |
| opsview-loadbalancer | Load Balancer | Distributed | Yes (5) |
| opsview-machinestats | Machine Stats | Distributed | Yes (4) |
| opsview-messagequeue | MessageQueue | Distributed | Yes (2) |
| opsview-notificationcenter | Notification Center | Distributed | Yes |
| opsview-orchestrator | Orchestrator | Orchestrator only | Yes |
| opsview-registry | Registry | Distributed | Yes (2) |
| opsview-resultsdispatcher | Results Dispatcher | Distributed | Yes (2) |
| opsview-resultsexporter | Results Exporter | Distributed | No - see Results Exporter for details. |
| opsview-resultsforwarder | Results Forwarder | Distributed | Yes (3) |
| opsview-resultslive | Results Live | Distributed | Yes (2) It is sharded (each resultslive node handles a specific subset of objects). |
| opsview-resultsperformance | Results Performance | Distributed | Yes (2) |
| opsview-resultsrecent | Results Recent | Distributed | Yes (2) |
| opsview-resultssender | Results Sender | Distributed | Yes (3) |
| opsview-scheduler | Scheduler | Distributed | Yes (3) |
| opsview-snmptraps | Snmp Traps Daemon | Distributed | No |
| opsview-snmptrapscollector | Snmp Traps Collector | Distributed | No |
| opsview-statechanges | State Changes | Distributed | Yes (2) |
| opsview-timeseries | TimeSeries | Distributed | Yes (2) It is sharded (each timeseries node handles a specific subset of objects) |
| opsview-timeseriesenqueuer | TimeSeries Enqueuer | Distributed | Yes (2) |
| opsview-timeseriesinfluxdbqueries | TimeSeries InfluxDB Queries | Distributed | Yes (1) |
| opsview-timeseriesinfluxdbupdates | TimeSeries InfluxDB Updates | Distributed | Yes (1) |
| opsview-timeseriesrrdqueries | TimeSeries RRD Queries | Distributed | Yes (1) |
| opsview-timeseriesrrdupdates | TimeSeries RRD Updates | Distributed | Yes (1) |
| opsview-watchdog | Watchdog | Distributed | Yes |
| opsview-web | Web | Orchestrator only | Yes |
| opsviewd | Daemon | Orchestrator only | Yes |
Footnote 1 Copied
RRD and InfluxDB could be used as alternatives — so either RRD Updates/Queries or InfluxDB Updates/Queries.
Footnote 2 Copied
Distributed components — can be installed and run on multiple servers but only one will be in use any any time.
Footnote 3 Copied
Collector components. One set will be installed on Orchestrator server — any extras are proper Collector Servers. Only Scheduler is actually required on Collector - everything else could be remote.
Footnote 4 Copied
Components that is installed on every box that uses Watchdog (with the exception of SSH Tunnels to avoid dependency on Registry).
Footnote 5 Copied
Could be installed anywhere and on multiple servers.
Components servers Copied
The below information is relevant if you are intending to run an advanced installation. Some example configuration files are provided with the opsview-deploy:
host1:~# cd /opt/opsview/deploy
host1:/opt/opsview/deploy# ls -l etc/examples
-rw-r--r-- 1 root root 1 Sep 28 00:00 opsview_deploy-01-xsmall.yml
-rw-r--r-- 1 root root 1 Sep 28 00:00 opsview_deploy-02-small.yml
-rw-r--r-- 1 root root 1 Sep 28 00:00 opsview_deploy-03-medium.yml
-rw-r--r-- 1 root root 1 Sep 28 00:00 opsview_deploy-04-large.yml
-rw-r--r-- 1 root root 1 Sep 28 00:00 opsview_deploy-05-xlarge.yml
For more information, follow the instructions on Advanced Automated Installation.
This is the list of Component servers:
Orchestrator server Copied
Purpose: Orchestrator Server manages configuration and provides UI
Load: High
Packages:
opsview-autodiscovery-manager
opsview-automonitor-manager
opsview-automonitor-scanner
opsview-core-utils
opsview-license-manager
opsview-orchestrator
opsview-web-app
opsview-web-app-server
opsview-webserver
includes Collector Server Components
Orchestrator MessageQueue server Copied
Purpose: Message Bus for communication between Result Processing Components
Load: High
Connected Components:
opsview-results-live
opsview-results-recent
opsview-results-sender
opsview-results-performance
opsview-results-snmp
opsview-results-forwarder
opsview-results-flow
opsview-results-dispatcher
opsview-orchestrator
opsview-autodiscovery-manager
opsview-autodiscovery-scanner
opsview-state-changes
opsview-scheduler
opsview-executor
opsview-snmptraps-collector
opsview-results-dispatcher
opsview-notification-center
opsview-freshness-checker
opsview-downtime-manager
opsview-bsm
Packages:
opsview-messagequeue
opsview-messagequeue-proxy
opsview-loadbalancer
Orchestator Datastore server Copied
Purpose: Persistent Datastore
Load: High
Connected Components:
opsview-results-live
opsview-orchestrator
opsview-bsm
opsview-notification-center
opsview-downtime-manager
Packages:
opsview-datastore
opsview-datastore-proxy
opsview-loadbalancer
Orchestrator Database server (remote) Copied
Purpose: Configuration and results Database
Load: High
Connected Components:
opsview-results-live
opsview-results-recent
opsview-orchestrator
opsview-autodiscovery-manager
opsview-state-changes
opsview-results-dispatcher
opsview-results-flow
opsview-results-snmp
opsview-servicedesk-connector
opsview-freshness-checker
opsview-downtime-manager
opsview-bsm
opsview-core-utils
Packages:
mysql-server
Collector Cluster MessageQueue server Copied
Purpose: Collector Cluster-wide Message Bus
Load: Mid-High (depending on Cluster size and amount of monitored objects)
Connected Components:
opsview-results-sender
opsview-scheduler
opsview-executor
opsview-results-forwarder
Packages:
opsview-messagequeue
opsview-registry-proxy
opsview-loadbalancer
Collector Cluster DataStore server Copied
Purpose: Persistent DataStore
Load: High
Connected Components:
opsview-scheduler
Packages:
opsview-datastore
opsview-registry-proxy
opsview-loadbalance
Results-Live server Copied
Purpose: Live objects status processing
Load: High
Packages:
opsview-results-live
opsview messagequeue-proxy
opsview-datastore-proxy
opsview-registry-proxy
opsview-loadbalancer
Results-Recent server Copied
Purpose: Gathering results for objects
Load: High
Packages:
opsview-results-recent
opsview-registry-proxy
opsview-messagequeue-proxy
opsview-loadbalancer
Results-Performance server Copied
Purpose: Preparing performance metrics to be send to TimeSeries
Load: Medium
Packages:
opsview-results-performance
ospview-messagequeue-proxy
opsview-registry-proxy
opsview-loadbalancer
Results-Dispatcher server Copied
Purpose: Routing passive results to Collectors
Load: Varies (depends on the amount of passive results)
Packages:
opsview-results-dispatcher
opsview-messagequeue-proxy
opsview-registry-proxy
opsview-loadbalancer
State-Changes server Copied
Purpose: Tracking state changes and notifying Notification Centre
Load: Medium/High
Packages:
opsview-state-changes
opsview-messagequeue-proxy
opsview-registry-proxy
opsview-loadbalancer
Periodic Components server Copied
Purpose: Periodic checks
Load: Medium
Packages:
opsview-downtime-manager
opsview-messagequeue-proxy
opsview-bsm
opsview-freshness-checker
Registry server Copied
Purpose: Service Discovery
Load: High
Packages:
opsview-registry
TimeSeries server Copied
Purpose: Processing and storing performance metrics
Load: High
Packages:
opsview-timeseries
opsview-timeseries-enqueuer
opsview-timeseries-rrd | opsview-timeseries-influxdb
Collector server Copied
Purpose: Hosts and services monitoring
Load: High
Packages:
infrastructure-agent
opsview-autodiscovery-scanner
opsview-datastore-proxy
opsview-executor
opsview-machine-stats
opsview-messagequeue-proxy
opsview-monitoring-scripts
opsview-monitoring-scripts-base
opsview-registry-proxy
opsview-results-forwarder
opsview-results-sender
opsview-scheduler
opsview-snmptraps-collector
opsview-watchdog