Google Pub Sub Metrics via Telegraf

Google Pub Sub Metrics via Telegraf

Ship your Google Pub Sub Metrics via Telegraf to your Logit.io Stack

Configure Telegraf to ship Google Pub Sub metrics to your Logit.io stacks via Logstash.

Install Integration

Please click on the Install Integration button to configure your stack for this source.

Set Credentials in GCP

@intro

  • Begin by heading over to the 'Project Selector' (opens in a new tab) and select the specific project from which you wish to send metrics.

    • Progress to the 'Service Account Details' screen. Here, assign a distinct name to your service account and opt for 'Create and Continue'.
    • In the 'Grant This Service Account Access to Project' screen, ensure the following roles: 'Compute Viewer', 'Monitoring Viewer', and 'Cloud Asset Viewer'.
    • Upon completion of the above, click 'Done'.
    • Now find and select your project in the 'Service Accounts for Project' list.
    • Move to the 'KEYS' section.
    • Navigate through Keys > Add Key > Create New Key, and specify 'JSON' as the key type.
    • Lastly, click on 'Create', and make sure to save your new key.

    Now add the environment variable for the key

    On the machine run:

    export GOOGLE_APPLICATION_CREDENTIALS=<your-gcp-key>

Install Telegraf

This integration allows you to configure a Telegraf agent to send your metrics, in multiple formats, to Logit.io.

Choose the installation method for your operating system:

When you paste the command below into Powershell it will download the Telegraf zip file. Once that is complete, press Enter again and the zip file will be extracted into C:\Program Files\InfluxData\telegraf\telegraf-1.31.2.

wget https://dl.influxdata.com/telegraf/releases/telegraf-1.31.2_windows_amd64.zip -UseBasicParsing -OutFile telegraf-1.31.2_windows_amd64.zip 
Expand-Archive .\telegraf-1.31.2_windows_amd64.zip -DestinationPath 'C:\Program Files\InfluxData\telegraf'

Configure the Telegraf input plugin

First you need to set up the input plug-in to enable Telegraf to scrape the GCP data from your hosts. This can be accomplished by incorporating the following code into your configuration file:

# Gather timeseries from Google Cloud Platform v3 monitoring API
[[inputs.stackdriver]]
  ## GCP Project
  project = "<your-project-name>"
 
  ## Include timeseries that start with the given metric type.
  metric_type_prefix_include = [
	"@metric_type",
  ]
 
  ## Most metrics are updated no more than once per minute; it is recommended
  ## to override the agent level interval with a value of 1m or greater.
  interval = "1m"

Read more about how to configure data scraping and configuration options for Stackdriver (opens in a new tab)

Configure the output plugin

Once you have generated the configuration file, you need to set up the output plug-in to allow Telegraf to transmit your data to Logit.io in Prometheus format. This can be accomplished by incorporating the following code into your configuration file:

[[outputs.http]]
  url = "https://@metricsUsername:@metricsPassword@@metrics_id-vm.logit.io:@vmAgentPort/api/v1/write"
  data_format = "prometheusremotewrite"
 
  [outputs.http.headers]
    Content-Type = "application/x-protobuf"
    Content-Encoding = "snappy"

Start Telegraf

From the location where Telegraf was installed (C:\Program Files\InfluxData\telegraf\telegraf-1.31.2) run the program providing the chosen configuration file as a parameter:

.\telegraf.exe --config telegraf-demo.conf

Once Telegraf is running you should see output similar to the following, which confirms the inputs, output and basic configuration the application has been started with: Powershell Telegraf information

View your metrics

Data should now have been sent to your Stack.

View My Data

If you don't see metrics take a look at How to diagnose no data in Stack below for how to diagnose common issues.

How to diagnose no data in Stack

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Telegraf Google Pub Sub Platform metrics Overview

Introduced to streamline data operations, Telegraf's plugin for Google Cloud Pub/Sub simplifies metrics collection from distributed systems and services, facilitating real-time analytics and monitoring. This integration is crucial for organizations leveraging cloud-native technologies, ensuring that they can efficiently collect, process, and monitor event data at scale.

However, the sheer volume and complexity of metrics data collected via Google Cloud Pub/Sub can be overwhelming. Logit.io provides a comprehensive solution for the efficient analysis and visualization of these metrics. Our platform enhances the capabilities of Telegraf by offering a powerful analytics toolset designed to handle the ingestion, processing, and visualization of vast amounts of data with ease. With Logit.io, users benefit from advanced features such as automated parsing, real-time alerts, and intuitive dashboards, all aimed at simplifying data management and accelerating insights.

For those integrating Telegraf with Google Cloud Pub/Sub and seeking to optimize their data analytics and monitoring strategies, Logit.io stands ready to support. Our platform not only streamlines data ingestion and analysis but also provides actionable insights that are essential for maintaining high-performance, reliable systems. Sending Data to Logit.io from Google Pub/Sub is a seamless way to enhance your log management and analytics capabilities. This integration empowers you to efficiently collect and analyze a wide range of data, from application logs to system metrics and event information. By centralizing your data in Logit.io, you gain access to a powerful set of tools for monitoring and gaining insights into your infrastructure's performance. For a deeper understanding of the metrics specific to Google Recommendations metrics and VPC peering be sure review these integrations to further explore your metrics. Enjoy the convenience of these integrations within Logit.io's service for GCP logging (opens in a new tab).