Google Cloud PubSub is a messaging queue (similar to Rabbit MQ) and ingestion solution for event-driven systems and streaming analytics. Once a message is read and acknowledged, it's gone, and therefore you may opt to have multiple copies of a message read by separate readers. This is done by creating subscriptions for that topic, where each subscription will have an entire copy of everything that goes into the topic. Google Cloud Pub/Sub is well-suited in Google Compute Engine instances with large sets of data that can be distributed efficiently.
Why use the Google Cloud PubSub Push Telegraf Plugin?
The Google Cloud PubSub Push listener is a service input plugin that listens for messages sent via an HTTP POST from Google Cloud PubSub. The intent of the plugin is to allow Telegraf to serve as an endpoint of the Google Pub/Sub 'Push' service. Google's PubSub service sends over HTTPS/TLS, and therefore the plugin must be behind a valid proxy or configured to use TLS.
Collecting your messages with the Google Cloud PubSub Push Telegraf Plugin will allow you to store your messages in InfluxDB along with all of your other metric and event data.
How to use the Google Cloud PubSub Push Telegraf Plugin
Using the Google Cloud PubSub Push Telegraf Plugin is simple. After installation, you can choose the configuration options that fit your environment (service address, tokens, timeouts, body size, etc). In addition, you can enable TLS by specifying the file names of a service TLS certificate and key. You can also enable mutually authenticated TLS and authorize client connections by signing certificate authority, by including a list of allowed CA certificate file names in
Please note that this plugin expects messages in the Google's Pub/Sub JSON Format ONLY.
Key Google Cloud PubSub Push metrics to use for monitoring
With Google Cloud PubSub Push, you can stream data between different applications, application monitoring, fraud detection and live leader-boards.