Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Monitoring Varnish Cache
Varnish is a web application accelerator. It is a reverse proxy that acts like a HTTP cache. Since it allows speeding up the service through content caching, it’s a very useful app for web apps or services with a high traffic volume. The typical app architecture used by HTTP cache is like the one below.

Once installed, Varnish Cache allows us to use several apps to evaluate the server by means of statistics.

With a Pandora FMS agent installed in the Varnish Cache machine and using the Varnish Cache monitoring plugin you can monitor things like:
  • client_conn : accepted client connections
  • client_req : received client requests
  • backend_fail : backend connection failure
  • cache_miss : cache misses
  • n_object : number of instantiated objects
  • n_wrk : number of worker threads
  • n_wrk_create : number of created worker threads
  • n_wrk_failed : number of failures when creating worker threads
  • n_wrk_max : maximum number of worker threads
  • n_wrk_drop : number of abandoned work requests
  • n_lru_nuked : number LRU objects
  • esi_errors : ESI parsing errors
  • n_expired: number of expired objects

Having all of them in a simple view:

[Image: 4.png]

With the possibility of create reports:

[Image: jk.png]

And configuring alerts that warns you when somthing go bad:

[Image: po.png]

Complete article with help step by step to monitoris your Vanish Cache system

Users browsing this thread: 1 Guest(s)

(c) 2006-2018 Artica Soluciones Tecnológicas. Contents of this wiki are under Create Common Attribution v3 licence. | |

Theme © MyBB Themes