Support Center

To better serve you during these uncertain times, we will be hosting a weekly support webinar. We’ll cover topics like LogicMonitor admin basics as well as ways to monitor a remote work environment. Tune in every Wednesday at 11:00am PST.

Sign up here

To better serve you during these uncertain times, we will be hosting a weekly support webinar. We’ll cover topics like LogicMonitor admin basics as well as ways to monitor a remote work environment. Tune in every Wednesday at 11:00am PST.

Sign up here

To monitor Varnish performance, LogicMonitor collector uses SNMP extensions to trigger a script, which runs ‘varnishstat -1’ command on the server.

To enable data collection, please do the following on each of your Varnish servers:

1. Create a script “varnishparse” in /usr/local/bin:

#!/bin/bash
/usr/bin/varnishstat -1 -f $1 | awk ' { print $2 } ' 

2. Put all of the following into the /etc/snmp/snmpd.conf file (after you’ve configured SNMP):

extend varnish-client-req /usr/local/bin/varnishparse client_req
extend varnish-client-conn /usr/local/bin/varnishparse client_conn
extend varnish-cache-hits /usr/local/bin/varnishparse cache_hit
extend varnish-cache-miss /usr/local/bin/varnishparse cache_miss
extend varnish-cache-hitpass /usr/local/bin/varnishparse cache_hitpass
extend varnish-backend-unused /usr/local/bin/varnishparse backend_unused
extend varnish-backend-unhealthy /usr/local/bin/varnishparse backend_unhealthy
extend varnish-backend-reuse /usr/local/bin/varnishparse backend_reuse
extend varnish-backend-recycle /usr/local/bin/varnishparse backend_recycle
extend varnish-backend-fail /usr/local/bin/varnishparse backend_fail
extend varnish-backend-busy /usr/local/bin/varnishparse backend_busy
extend varnish-backend-conn /usr/local/bin/varnishparse backend_conn
extend varnish-s-sess /usr/local/bin/varnishparse s_sess
extend varnish-s-req /usr/local/bin/varnishparse s_req
extend varnish-s-pipe /usr/local/bin/varnishparse s_pipe
extend varnish-s-fetch /usr/local/bin/varnishparse s_fetch
extend varnish-s-pass /usr/local/bin/varnishparse s_pass
extend varnish-s-hdrbytes /usr/local/bin/varnishparse s_hdrbytes
extend varnish-s-bodybytes /usr/local/bin/varnishparse s_bodybytes
extend varnish-n-object /usr/local/bin/varnishparse n_object
extend varnish-n-wrk /usr/local/bin/varnishparse n_wrk
extend varnish-n-wrk-max /usr/local/bin/varnishparse n_wrk_max
extend varnish-n-wrk-overflow /usr/local/bin/varnishparse n_wrk_overflow
extend varnish-n-wrk-drop /usr/local/bin/varnishparse n_wrk_drop
extend varnish-n-lru-nuked /usr/local/bin/varnishparse n_lru_nuked
extend varnish-n-expired /usr/local/bin/varnishparse n_expired
extend varnish-n-wrk-queue /usr/local/bin/varnishparse n_wrk_queue
extend varnish-n-wrk-failed /usr/local/bin/varnishparse n_wrk_failed
extend varnish-n-wrk-create /usr/local/bin/varnishparse n_wrk_create 

3. Restart snmpd (service snmpd restart).

After you complete the steps above, the Varnish Performance datasource will be associated with proper hosts, and the monitoring will start automatically.

In this Article: