Adding upstream version 1.34.4.
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
parent
e393c3af3f
commit
4978089aab
4963 changed files with 677545 additions and 0 deletions
48
plugins/outputs/signalfx/README.md
Normal file
48
plugins/outputs/signalfx/README.md
Normal file
|
@ -0,0 +1,48 @@
|
|||
# SignalFx Output Plugin
|
||||
|
||||
This plugin writes metrics to [SignalFx][docs].
|
||||
|
||||
⭐ Telegraf v1.18.0
|
||||
🏷️ applications
|
||||
💻 all
|
||||
|
||||
[docs]: https://docs.signalfx.com/en/latest/
|
||||
|
||||
## Global configuration options <!-- @/docs/includes/plugin_config.md -->
|
||||
|
||||
In addition to the plugin-specific configuration settings, plugins support
|
||||
additional global and plugin configuration settings. These settings are used to
|
||||
modify metrics, tags, and field or create aliases and configure ordering, etc.
|
||||
See the [CONFIGURATION.md][CONFIGURATION.md] for more details.
|
||||
|
||||
[CONFIGURATION.md]: ../../../docs/CONFIGURATION.md#plugins
|
||||
|
||||
## Secret-store support
|
||||
|
||||
This plugin supports secrets from secret-stores for the `access_token` option.
|
||||
See the [secret-store documentation][SECRETSTORE] for more details on how
|
||||
to use them.
|
||||
|
||||
[SECRETSTORE]: ../../../docs/CONFIGURATION.md#secret-store-secrets
|
||||
|
||||
## Configuration
|
||||
|
||||
```toml @sample.conf
|
||||
# Send metrics and events to SignalFx
|
||||
[[outputs.signalfx]]
|
||||
## SignalFx Org Access Token
|
||||
access_token = "my-secret-token"
|
||||
|
||||
## The SignalFx realm that your organization resides in
|
||||
signalfx_realm = "us9" # Required if ingest_url is not set
|
||||
|
||||
## You can optionally provide a custom ingest url instead of the
|
||||
## signalfx_realm option above if you are using a gateway or proxy
|
||||
## instance. This option takes precedence over signalfx_realm.
|
||||
ingest_url = "https://my-custom-ingest/"
|
||||
|
||||
## Event typed metrics are omitted by default,
|
||||
## If you require an event typed metric you must specify the
|
||||
## metric name in the following list.
|
||||
included_event_names = ["plugin.metric_name"]
|
||||
```
|
Loading…
Add table
Add a link
Reference in a new issue