2019-01-04 00:20:07 +00:00
|
|
|
# Google Cloud PubSub Input Plugin
|
|
|
|
|
|
|
|
The GCP PubSub plugin ingests metrics from [Google Cloud PubSub][pubsub]
|
|
|
|
and creates metrics using one of the supported [input data formats][].
|
|
|
|
|
|
|
|
|
|
|
|
### Configuration
|
|
|
|
|
|
|
|
```toml
|
|
|
|
[[inputs.pubsub]]
|
|
|
|
## Required. Name of Google Cloud Platform (GCP) Project that owns
|
|
|
|
## the given PubSub subscription.
|
|
|
|
project = "my-project"
|
|
|
|
|
|
|
|
## Required. Name of PubSub subscription to ingest metrics from.
|
|
|
|
subscription = "my-subscription"
|
|
|
|
|
|
|
|
## Required. Data format to consume.
|
|
|
|
## Each data format has its own unique set of configuration options.
|
|
|
|
## Read more about them here:
|
|
|
|
## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
|
|
|
|
data_format = "influx"
|
|
|
|
|
2019-01-04 00:28:15 +00:00
|
|
|
## Optional. Filepath for GCP credentials JSON file to authorize calls to
|
|
|
|
## PubSub APIs. If not set explicitly, Telegraf will attempt to use
|
|
|
|
## Application Default Credentials, which is preferred.
|
2019-01-04 00:20:07 +00:00
|
|
|
# credentials_file = "path/to/my/creds.json"
|
|
|
|
|
2019-02-21 01:33:56 +00:00
|
|
|
## Optional. Number of seconds to wait before attempting to restart the
|
|
|
|
## PubSub subscription receiver after an unexpected error.
|
|
|
|
## If the streaming pull for a PubSub Subscription fails (receiver),
|
|
|
|
## the agent attempts to restart receiving messages after this many seconds.
|
|
|
|
# retry_delay_seconds = 5
|
|
|
|
|
2019-01-04 00:28:15 +00:00
|
|
|
## Optional. Maximum byte length of a message to consume.
|
|
|
|
## Larger messages are dropped with an error. If less than 0 or unspecified,
|
2019-01-04 00:20:07 +00:00
|
|
|
## treated as no limit.
|
|
|
|
# max_message_len = 1000000
|
|
|
|
|
2019-01-04 00:28:15 +00:00
|
|
|
## Optional. Maximum messages to read from PubSub that have not been written
|
2019-01-04 00:20:07 +00:00
|
|
|
## to an output. Defaults to %d.
|
|
|
|
## For best throughput set based on the number of metrics within
|
|
|
|
## each message and the size of the output's metric_batch_size.
|
|
|
|
##
|
2019-01-04 00:28:15 +00:00
|
|
|
## For example, if each message contains 10 metrics and the output
|
2019-01-04 00:20:07 +00:00
|
|
|
## metric_batch_size is 1000, setting this to 100 will ensure that a
|
|
|
|
## full batch is collected and the write is triggered immediately without
|
|
|
|
## waiting until the next flush_interval.
|
|
|
|
# max_undelivered_messages = 1000
|
|
|
|
|
|
|
|
## The following are optional Subscription ReceiveSettings in PubSub.
|
|
|
|
## Read more about these values:
|
|
|
|
## https://godoc.org/cloud.google.com/go/pubsub#ReceiveSettings
|
2019-01-04 00:28:15 +00:00
|
|
|
|
2019-01-04 00:20:07 +00:00
|
|
|
## Optional. Maximum number of seconds for which a PubSub subscription
|
|
|
|
## should auto-extend the PubSub ACK deadline for each message. If less than
|
|
|
|
## 0, auto-extension is disabled.
|
|
|
|
# max_extension = 0
|
|
|
|
|
2019-01-04 00:28:15 +00:00
|
|
|
## Optional. Maximum number of unprocessed messages in PubSub
|
|
|
|
## (unacknowledged but not yet expired in PubSub).
|
|
|
|
## A value of 0 is treated as the default PubSub value.
|
2019-01-04 00:20:07 +00:00
|
|
|
## Negative values will be treated as unlimited.
|
|
|
|
# max_outstanding_messages = 0
|
|
|
|
|
2019-01-04 00:28:15 +00:00
|
|
|
## Optional. Maximum size in bytes of unprocessed messages in PubSub
|
|
|
|
## (unacknowledged but not yet expired in PubSub).
|
|
|
|
## A value of 0 is treated as the default PubSub value.
|
2019-01-04 00:20:07 +00:00
|
|
|
## Negative values will be treated as unlimited.
|
|
|
|
# max_outstanding_bytes = 0
|
|
|
|
|
2019-01-04 00:28:15 +00:00
|
|
|
## Optional. Max number of goroutines a PubSub Subscription receiver can spawn
|
|
|
|
## to pull messages from PubSub concurrently. This limit applies to each
|
|
|
|
## subscription separately and is treated as the PubSub default if less than
|
|
|
|
## 1. Note this setting does not limit the number of messages that can be
|
2019-01-04 00:20:07 +00:00
|
|
|
## processed concurrently (use "max_outstanding_messages" instead).
|
|
|
|
# max_receiver_go_routines = 0
|
2019-03-07 01:34:47 +00:00
|
|
|
|
|
|
|
## Optional. If true, Telegraf will attempt to base64 decode the
|
|
|
|
## PubSub message data before parsing. Many GCP services that
|
|
|
|
## output JSON to Google PubSub base64-encode the JSON payload.
|
|
|
|
# base64_data = false
|
2019-01-04 00:20:07 +00:00
|
|
|
```
|
|
|
|
|
|
|
|
### Multiple Subscriptions and Topics
|
|
|
|
|
|
|
|
This plugin assumes you have already created a PULL subscription for a given
|
|
|
|
PubSub topic. To learn how to do so, see [how to create a subscription][pubsub create sub].
|
|
|
|
|
2019-01-04 00:28:15 +00:00
|
|
|
Each plugin agent can listen to one subscription at a time, so you will
|
2019-01-04 00:20:07 +00:00
|
|
|
need to run multiple instances of the plugin to pull messages from multiple
|
|
|
|
subscriptions/topics.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[pubsub]: https://cloud.google.com/pubsub
|
|
|
|
[pubsub create sub]: https://cloud.google.com/pubsub/docs/admin#create_a_pull_subscription
|
|
|
|
[input data formats]: /docs/DATA_FORMATS_INPUT.md
|