/
Monitoring Service Check: varnish_controller

Welcome to the VSHN Knowledge Base

Monitoring Service Check: varnish_controller

Owned by Pierre Rouveyrol
Last updated: 2024-07-10

Overview

This checks several components of varnish_controller.

  • varnishd is checked with TCP
  • brainz with procs
  • api-gw with TCP
  • nats with TCP
  • UI with TCP
  • agent with procs

The systemd services are :

  • varnish_controller_agent
  • varnish_controller_varnishd
  • varnish_controller_brainz
  • varnish_controller_api_gw
  • varnish_controller_nats
  • varnish_controller_ui

Logs for all services should be handled by journald.


Technical Details

Implementation

Global base checkMo
Puppet profiles using this checkprofile_varnish

Check plugins

Namecheck_procs, check_tcp
Packagesicinga2-common, monitoring-plugins-basic
CheckCommand namecheck_procs, check_tcp
Upstream source linkpart of icinga2 base installation
Documentation linkhttps://icinga.com/docs/icinga-2/latest/doc/10-icinga-template-library/#tcp
https://icinga.com/docs/icinga-2/latest/doc/10-icinga-template-library/#procs

List of variables

See documentations above for details

Icinga2 variableConfigured inDefault ValueDescription
procs_criticalset the expected number of procs (1:)
The expected number of processes to run

procs_argument

Name of the process to find

Name of process to monitor

Icinga2 variableConfigure inDefault value

Description

tcp_addressset to the ip address to which the service binds to in the profile
the IP address where the check connects to
tcp_portset to port the service binds to
the port where the check connects to


Troubleshooting/Known issues

A service is alerting

Solution

A systemd service restart should do the trick.

Tuning




Related content