Aliaksandr Valialkin
4f6d33af07
Urls to docs.victoriametrics.com, which do not end with `/`, are working, but they lead to an unnecessary redirect to /index.html url,
which breaks backwards navigation. For example, https://docs.victoriametrics.com/victoriametrics/integrations/prometheus
redirects to https://docs.victoriametrics.com/victoriametrics/integrations/prometheus/index.html .
So it is better to consistently end all the urls to docs.victoriametrics.com with `/` in order to prevent
the unnecessary redirect and preserve backwards navigation. E.g. https://docs.victoriametrics.com/victoriametrics/integrations/prometheus
is replaced with https://docs.victoriametrics.com/victoriametrics/integrations/prometheus/ , etc.
This is a follow-up for commits starting from 4701fec7b2
4.1 KiB
title, weight, menu, tags, aliases
| title | weight | menu | tags | aliases | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Telegraf | 5 |
|
|
|
This document covers various output configurations for Telegraf for shipping data via HTTP to VictoriaMetrics. All the options examples below can be combined to fit your use case.
To avoid storing Passwords in configuration files you can store as a key value pair in /etc/default/telegraf on Linux as follows
victoriametrics_url="https://victoriametrics_url"
victoriametrics_user="telegraf"
victoriametrics_password="password"
victoriametrics_token="my_token"
and they can be referenced in a Telegraf configuration file by prepending the variable name with $.
For example, $victoriametrics_url will be translated to https://victoriametrics_url if it is referenced in a Telegraf configuration using the values from /etc/default/telegraf in the values seen above.
Otherwise, please replace the variables below to fit your setup.
If you want to mimic this behavior on Windows please read Influx Data's blog on storing variables in the registry For shipping data in InfluxDB v2.x format refer to Telegraf docs.
Minimum Configuration with no Authentication
[[outputs.influxdb]]
urls = ["$victoriametrics_url"]
database = "victoriametrics"
skip_database_creation = true
exclude_retention_policy_tag = true
content_encoding = "gzip"
HTTP Basic Authentication (Username and Password)
This is the same as the minimum configuration, but adds the username and password options:
[[outputs.influxdb]]
urls = ["$victoriametrics_url"]
username = "$victoriametrics_user"
password = "$victoriametrics_password"
database = "victoriametrics"
skip_database_creation = true
exclude_retention_policy_tag = true
content_encoding = "gzip"
Bearer Authentication (Token)
This is the same as the minimum configuration but adds the authorization header:
[[outputs.influxdb]]
urls = ["$victoriametrics_url"]
http_headers = {"Authorization" = "Bearer $victoriametrics_token"}
database = "victoriametrics"
skip_database_creation = true
exclude_retention_policy_tag = true
content_encoding = "gzip"
Route certain metrics
If you only want to route certain metrics to VictoriaMetrics use the namepass option with a comma separated list of the measurements you wish to send to VictoriaMetrics:
[[outputs.influxdb]]
urls = ["$victoriametrics_url"]
username = "$victoriametrics_user"
password = "$victoriametrics_password"
database = "victoriametrics"
skip_database_creation = true
exclude_retention_policy_tag = true
content_encoding = "gzip"
namepass = ["cpu","disk","measurement1","measurement2"]
Ignore TLS/SSL Certificate errors
This is the same as the minimum configuration but adds insecure_skip_verify = true to the configuration to ignore TLS certificate errors.
This is not recommended since it can allow sending metrics to a compromised site.
[[outputs.influxdb]]
urls = ["$victoriametrics_url"]
username = "$victoriametrics_user"
password = "$victoriametrics_password"
database = "victoriametrics"
skip_database_creation = true
exclude_retention_policy_tag = true
content_encoding = "gzip"
insecure_skip_verify = true