Chat now with support
Chat with Support

syslog-ng Store Box 6.1.0 - Administration Guide

Preface Introduction The concepts of SSB The Welcome Wizard and the first login Basic settings User management and access control Managing SSB Configuring message sources Storing messages on SSB Forwarding messages from SSB Log paths: routing and processing messages Configuring syslog-ng options Searching log messages Searching the internal messages of SSB Classifying messages with pattern databases The SSB RPC API Monitoring SSB Troubleshooting SSB Security checklist for configuring SSB

Monitoring SSB

This section describes monitoring SSB.

If you intend to monitor SSB, the general rules of monitoring an Ubuntu system apply.

Depending on your monitoring tool, check out the available SNMP templates related to your system, and use those to monitor the general parts of SSB. These are the following:

Caution:

Do not install any monitoring agent on the SSB appliance. Any alteration to the system is unsupported.

For details on receiving e-mail alerts or SNMP traps on health- and system-related issues, see Configuring system monitoring on SSB.

Monitoring SSB's disk

SNMP object: HOST-RESOURCES-MIB::hrStorageTable

This section describes monitoring SSB's disk usage. Disk usage is measured per mountpoint (that is, partition).

Master
Mountpoint /mnt/firmware
Partition core firmware partition
Community

<community-of-master-node> (Basic Settings > Management > SNMP agent settings > Community)

Context "" (empty string)

Free disk space that can be acquired by your main production system (for example, logspaces).

To make sure that you have the free disk space you are comfortable with, monitor the free disk space. This partition can fill up with for example the following:

  • received logs

  • generated reports

  • collected statistics

  • core dumps

If you cannot keep your free disk space in your comfortable interval (with scheduled cleanups) you probably need to purchase more SSB appliances. For assistance, contact our Support Team.

NOTE:

If you have configured Basic Settings > Monitoring & Disk space fill up prevention, be aware that SSB will stop receiving log after reaching the configured threshold. By default, clients are disconnected when disks are 90 percent full. For details, see Preventing disk space fill up.

Nodes
Mountpoint /initrd/mnt
Partition boot firmware partition (if SSB is in HA mode, the boot firmware partition of both nodes)
Community <id-of-the-node>
Context <id-of-the-node>

The space on this mountpoint is required only by the system. Generally, this is independent from how you use SSB. The only important thing here to have some free space on the mountpoint.

Make sure that you have some free space on this mountpoint. As a recommended threshold, set a trigger to 80% in your monitoring system. If there is only about 20% free space left on this mountpoint, contact our Support Team.

NOTE:

Monitoring the size of specific logspaces is not possible this way. If you are interested in the size of a specific logspace, you can configure a size limit alert for that logspace on the SSB web interface. For details on configuring a disk size alert for a specific logspace, see Creating logstores.

Monitoring SSB's memory

Swap usage
SNMP object:
  • UCD-SNMP-MIB::memTotalSwap

  • UCD-SNMP-MIB::memAvailSwap

SSB is using swap (except on Azure) as part of its normal operation.

You can receive swap usage alerts by configuring an alert on Basic Settings > Alerting & Monitoring. For details, see Configuring system monitoring on SSB.

Memory usage
SNMP object:
  • UCD-SNMP-MIB::memTotalReal

  • UCD-SNMP-MIB::memAvailReal

If SSB's memory and swap usage are both above 90%, fine-tune your configuration or purchase more SSB appliances to balance the load. For assistance, contact our Support Team.

Monitoring SSB's CPU

This section describes monitoring SSB's CPU.

NOTE:

This document uses the concept of 'logical CPU' used by the Linux kernel. In this section, 'logical CPU' will be abbreviated as 'CPU'. To determine the number of CPUs in your SSB machine, enter the lscpu command in your console, or send an SNMP request.

Related Documents