Google Storage Transfer Metrics via Telegraf

Google Storage Transfer Metrics via Telegraf

Ship your Google Storage Transfer Metrics via Telegraf to your Logit.io Stack

Configure Telegraf to ship Google Storage Transfer 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 Storage Transfer Platform metrics Overview

Integrating Telegraf with Google Cloud Storage Transfer Service allows for the monitoring of transfer operations, providing metrics on the success rates, latencies, and throughput of data movements. This level of insight is critical for businesses that rely on data-intensive operations, ensuring data availability and integrity while optimizing the performance of storage transfers.

However, managing and analyzing the metrics generated from these data transfers can become a significant challenge due to the volume and complexity of the data involved. Logit.io offers a streamlined solution for this issue, with a platform that excels in the ingestion, transformation, and analysis of log and metrics data from Telegraf and Google Cloud Storage Transfer Service.

Logit.io enhances the value of Telegraf's metrics by providing deep insights into the efficiency and reliability of data transfer processes. With our comprehensive analytics and monitoring tools, organizations can swiftly identify and resolve issues, optimize their data transfer strategies, and ensure that their data ecosystems operate smoothly.

With Google Storage Transfer Service, you can effortlessly transfer large volumes of data to Logit.io, a leading log management and analytics platform. This integration allows you to centralize your logs, making it easier to monitor and analyze data, which is crucial for maintaining the health and security of your applications. To streamline this process further, you can also utilize our Google App Engine integration. Moreover, for comprehensive monitoring and reporting, Google Managed Service Active Directory Metrics can be a valuable addition. By integrating this service with Logit.io, you can gain insights into the metrics related to your Active Directory infrastructure, providing a holistic view of your network and user activities. Logit.io's GCP logging (opens in a new tab) benefits from these seamless integrations.