influx telegrafs rm
The influx telegrafs rm command removes Telegraf configurations from InfluxDB.
Usage
influx telegrafs rm [flags]
Command aliases
rm, remove
Flags
| Flag | Description | Input type | Maps to ? | |
|---|---|---|---|---|
-c |
--active-config |
CLI configuration to use for command | string | |
--configs-path |
Path to influx CLI configurations (default ~/.influxdbv2/configs) |
string | INFLUX_CONFIGS_PATH |
|
-h |
--help |
Help for the rm command |
||
--hide-headers |
Hide the table headers | INFLUX_HIDE_HEADERS |
||
-i |
--id |
Telegraf configuration ID to remove | stringArray | |
--json |
Output data as json | INFLUX_OUTPUT_JSON |
||
--skip-verify |
Skip TLS certificate verification | INFLUX_SKIP_VERIFY |
||
-t |
--token |
API token | string | INFLUX_TOKEN |
Examples
Authentication credentials
The examples below assume your InfluxDB host, organization, and token are
provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN).
If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:
--host: InfluxDB host-o, --orgor--org-id: InfluxDB organization name or ID-t, --token: InfluxDB API token
Remove a Telegraf configuration
influx telegrafs rm --id ab12cd34ef56
Remove multiple Telegraf configurations
influx telegrafs rm \
--i 0Xx0oox00XXoxxoo1 \
--i oox0Xx0ox00XXxoo2
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.