Live Workshop: Integrate Google SecOps with Bindplane - Join Us on January 29th at 11 AM ET!Sign Up Now
Technical “How-To’s”

How to Monitor Varnish with Google Cloud Platform

Jonathan Wamsley
Jonathan Wamsley
Share:

We’re excited to announce that we’ve recently added Varnish monitoring support for the Google Cloud Platform. You can check it out here!

Below are steps to get up and running quickly with observIQ’s Google Cloud Platform integrations and monitor metrics and logs from Varnish in your Google Cloud Platform. You can check out Google’s documentation for using the Ops Agent for Varnish here.

What signals matter?

Varnish is a popular content streaming technology. Important metrics include information from clients, performance, threads, and backend.

  • Client Metrics
    • Connections
    • Requests
  • Performance Metrics
    • Cache Hits
    • Evictions
  • Thread Metrics
    • Creations
    • Failures
  • Backend Metrics
    • Success
    • Failures
    • General Health

The Varnish receiver can gather all the above categories – so let’s get started.

Related Content: Exploring & Remediating Consumption Costs with Google Billing and BindPlane OP

Before you begin

If you don’t already have an Ops Agent installed with the latest Varnish receiver, you’ll need to do that first. Check out the Google Cloud Platform Ops Agent documentation for installation methods, including the one-line installer.

Configuring the Varnish receiver for Metrics and Logs

Navigate to your Ops Agent configuration file. You’ll find it in the following location:

  • /etc/google-cloud-ops-agent/config.yaml (Linux)

Edit the configuration file for Varnish metrics as shown below:

yaml
1metrics:
2  receivers:
3    varnish:
4      type: varnish
5  service:
6    pipelines:
7      varnish:
8        receivers:
9          - varnish

For Logging, add the following in the same yaml config file:

yaml
1logging:
2  receivers:
3    varnish:
4      type: varnish
5  service:
6    pipelines:
7      varnish:
8        receivers:
9          - varnish

Related Content: Getting Started with BindPlane OP and Google Cloud Operations

Restart the Ops Agent with the following command:

sudo service google-cloud-ops-agent restart

sleep 30

Viewing the metrics collected

So that you know – the following Varnish metrics will now be delivered to your preferred destination following the steps detailed above.

MetricDescription
varnish.backend.connection.countThe backend connection type count.
varnish.cache.operation.countThe cache operation type count.
varnish.thread.operation.countThe thread operation type count.
varnish.session.countThe session connection type count.
varnish.object.nukedThe objects that have been forcefully evicted from storage count.
varnish.object.movedThe moved operations done on the LRU list count.
varnish.object.expiredThe expired objects from old age count.
varnish.object.countThe HTTP objects in the cache count.
varnish.client.request.countThe client request count.
varnish.client.request.error.countThe client request errors received by status code.
varnish.backend.request.countThe backend requests count.

Varnish is a high-performance web application accelerator that caches requests and delivers content. observIQ’s monitoring technology is a game changer for organizations that care about performance and efficiency. If you’re using Varnish, our solutions can significantly impact your infrastructure monitoring. Follow this space to keep up with all our future posts and simplified configurations for various sources.

For questions, requests, and suggestions, contact our support team at support@observIQ.com or join us on Slack!

Jonathan Wamsley
Jonathan Wamsley
Share:

Related posts

All posts

Get our latest content
in your inbox every week

By subscribing to our Newsletter, you agreed to our Privacy Notice

Community Engagement

Join the Community

Become a part of our thriving community, where you can connect with like-minded individuals, collaborate on projects, and grow together.

Ready to Get Started

Deploy in under 20 minutes with our one line installation script and start configuring your pipelines.

Try it now