Welcome to docs.opsview.com

Designing Your System

Scalability Considerations

Variables affecting how many devices can be monitored

  • Number of service checks per host
  • Median interval for service checks
  • Type of checks being executed (quality of plugin code, local execution vs agent queries, etc)
  • Network latency
  • Stability of system being monitored (number of host / service state changes per minute)

We recommend 250 hosts as a comfortable limit for single Opsview servers based on the following assumptions:

  1. 10 service checks per host (median)
  2. 5 minute interval per service check (median)
  3. Majority of service checks are against remote agent (NRPE / SNMP)
  4. Majority of monitored hosts are on same LAN
  5. System is stable with little flux

This results in approximately 10 service checks per second being executed by the monitoring server.

Databases

There are 2 databases used by Opsview Core:

  • Opsview - main configuration and access control
  • Runtime - status data and short term history

More information in the MySQL performance tuning section.

Disk partitioning

Opsview system

One large / partition is fine, but we recommend a partitioning schema of at least /, /boot and /var

  • / - Sufficient space for Operating System and upgrades
  • /boot - Recommend separate boot partition of 256MB
  • /usr/local - Opsview software is installed here. Recommend > 10GB

Database system

The databases will be stored on the same server as Opsview. Check filesystem:

  • /var - Opsview database and backups are stored here

Backups

By default, the nightly backups are in /usr/local/nagios/var/backups. It is recommended to change this to a different partition on a different physical disk for redundancy.

Security

Opsview Web Authentication

Opsview's web authentication uses an authentication ticket with a shared secret. Ensure this is set to a unique value for your instance.

Network

Opsview servers should be located in a secure area of your network. If you allow Opsview to be available on a public network, we recommend a firewall to restrict access to various ports. See this page for ports used by Opsview.

Credentials For Remote Services

If you need to connect to remote services (such as to an SNMP agent, a database, a VMware system or a Windows machine), you should use credentials with the minimum access required to achieve the desired monitoring.

SELinux

Opsview is not currently compatible with Security-Enhanced Linux extensions, this must be disabled.

Edit /etc/selinux/config and restart system:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
# SELINUXTYPE=targeted

System Settings

Time Zone

The Unix server can be set to any time zone. This will affect the times displayed in the web interface.

All data stored in databases and files will be forced to be UTC for consistency.

Navigation
Print/export
Toolbox