Welcome to docs.opsview.com

System Preferences

Web

Opsview Web Server

This is the web server for accessing the web interface of Opsview.

If this field has not been saved before, the field will be automatically populated based on the URL.

At reload time, if this system preference has not been saved, Opsview will use the master server's hostname (or IP).

Show Timeline

This controls the default value for whether to show the time line when the page first loads in the Events view.

Network Map Layout

This refers to the default layout of the Network Map.

  • Depth Layers
  • Collapsed Tree
  • Balanced Tree (default) - display the master server in the middle of the page with all parent/child relationships beneath
  • Circular - the master server is in the middle of the page with all parent child relationships linked radially, with distance related to the number of relationships between a host and the master server
  • Circular (Marked Up) - see Circular, but also includes clearer markings for distance from master server

Refresh rate

The refresh rate / refresh interval field specifies how frequently (in seconds) pages within the Opsview GUI will automatically refresh. A page refresh can be performed manually by clicking the refresh button within the Opsview GUI.

Audit log retention

Specifies how long in days that the audit logs are kept for. If you set this to 0, logs will never be removed.

The tables pruned based on this variable in runtime are:

  • nagios_contactnotificationmethods
  • nagios_contactnotifications
  • nagios_notifications
  • nagios_statehistory
  • nagios_commenthistory
  • nagios_acknowledgements
  • nagios_flappinghistory
  • nagios_downtimehistory
  • nagios_eventhandlers

These tables are pruned of data older than 7 days:

  • nagios_servicechecks
  • nagios_hostchecks

These tables are pruned of data older than 7 days. It is only used for debugging purposes:

  • nagios_conninfo

The housekeeping job runs overnight.

Smart Host Template Removal

From Opsview 3.11.1.

If a host template is removed from a host, via the host edit page or the host template edit page, then if this flag is set, then any appropriate host specific monitors will be removed unless the host monitor is also referenced in another host template that this host has.

For example, assume hostA has two host templates, Unix Base and Unix Backup. The Unix Base host template has two service checks, Loadavg and Memory. The Unix Backup host template has Loadavg only. The host also has two host exceptions for both Loadavg and Memory.

If hostA has the Unix Base host template removed, then if this flag is set, the host exception for Memory is removed. If it was not removed, then on an reload, Memory would be created as a service because it is still referenced as a host specific monitor. Note that Loadavg would not be removed because it is still referenced in the Unix Backup host template.

The default value for this is on as this is a useful behaviour.

Set Downtime on Host Delete

In Opsview since 2012-05-28

When a host is deleted, Opsview will automatically add +7d downtime to the host thus suppressing notifications before a reload occurs. This is especially useful in larger environments were reloads may take some time or are scheduled for a later time.

The default value is on as this is a useful behaviour.

Note: If you restore a previous database configuration so that the live monitoring has never seen the host being removed, then the host will remain in a downtime state. You will need to manually cancel the downtime.

Hostgroup information URL

URL constructed using macros to use instead of the default wiki information pages, specifically for hostgroup information.

Available macros are:

  • $HOSTGROUPNAME$ - name of hostgroup

Host information URL

URL constructed using macros to use instead of the default wiki information pages, specifically for host information.

Available macros are:

  • $HOSTADDRESS$ - primary hostname/IP of the host
  • $HOSTNAME$ - title of the host

Service information URL

URL constructed using macros to use instead of the default wiki information pages, specifically for service information. This is available from version 3.13.1.

Available macros are:

  • $HOSTADDRESS$ - primary hostname/IP of host
  • $HOSTNAME$ - title of the host
  • $SERVICENAME$ - name of service
  • $SERVICECHECKNAME$ - name of service check

Netdisco URL

Enter a URL to your Netdisco instance. It should be of the form:

http://server.example.com/netdisco

A link will be added to Netdisco on the Host Interface page.

You can also search a device on your Netdisco instance if you type in the Search Host box: nd hostname.

Nagios Core

Date Format

Change the general date format.

OptionFormatExample Date
USMM/DD/YYYY HH:MM:SS02/29/2012 16:45:00
Euro (Default)DD/MM/YYYY HH:MM:SS29/02/2012 16:45:00
ISO-8601YYYY-MM-DD HH:MM:SS2012-02-29 16:45:00
Strict ISO-8601YYYY-MM-DDTHH:MM:SS2012-02-29T16:45:00

Soft State Dependencies

This option determines whether or not NagiosĀ® Core will use soft service state information when checking service dependencies. Normally Nagios Core will only use the latest hard service state when checking dependencies. If you want it to use the latest state (regardless of whether its a soft or hard state type), enable this option.

You can define dependencies in the service check configuration.

Log Notifications

Logs when a notification is sent out. Useful.

Log Event Handlers

Logs when an event handler script is invoked. Useful.

Log Service Retries

Logs when a service is in a soft failure state. Useful, especially when debugging event handlers.

Log Host Retries

Logs when a host is in a soft failure state. Useful, especially when debugging event handlers.

Log Passive Checks

This logs every passive check into the Nagios Core log file.

Note: In a distributed environment, this will produce a large number of log entries on the master. Only switch on for short periods of time.

Enable Core Dumps

Used for debugging if you find that Nagios Core unexpectedly crashes.

Core dumps will be written to the nagios user's home directory. Check that the nagios user can write to their home directory and that ulimit -c is not zero.

If you see the following in the nagios.log file:

[1274862094] Caught SIGSEGV, shutting down...

Then a core dump will not be produced, because the nagios daemon would have handled a SIGSEGV signal, instead of allowing the OS to produce a core dump.

Navigation
Print/export
Toolbox