OpenTelemetry 输出插件
此插件通过 gRPC 将指标写入OpenTelemetry 服务器和代理。
引入于: Telegraf v1.20.0 标签: logging, messaging 操作系统支持: all
全局配置选项
插件支持其他全局和插件配置设置,用于修改指标、标签和字段,创建别名以及配置插件顺序等任务。更多详情请参阅 CONFIGURATION.md。
配置
# Send OpenTelemetry metrics over gRPC
[[outputs.opentelemetry]]
## Override the default (localhost:4317) OpenTelemetry gRPC service
## address:port
# service_address = "localhost:4317"
## Override the default (5s) request timeout
# timeout = "5s"
## Optional TLS Config.
##
## Root certificates for verifying server certificates encoded in PEM format.
# tls_ca = "/etc/telegraf/ca.pem"
## The public and private key pairs for the client encoded in PEM format.
## May contain intermediate certificates.
# tls_cert = "/etc/telegraf/cert.pem"
# tls_key = "/etc/telegraf/key.pem"
## Use TLS, but skip TLS chain and host verification.
# insecure_skip_verify = false
## Send the specified TLS server name via SNI.
# tls_server_name = "foo.example.com"
## Override the default (gzip) compression used to send data.
## Supports: "gzip", "none"
# compression = "gzip"
## NOTE: Due to the way TOML is parsed, tables must be at the END of the
## plugin definition, otherwise additional config options are read as part of
## the table
## Configuration options for the Coralogix dialect
## Enable the following section of you use this plugin with a Coralogix endpoint
# [outputs.opentelemetry.coralogix]
# ## Your Coralogix private key (required).
# ## Please note that this is sensitive data!
# private_key = "your_coralogix_key"
#
# ## Application and subsystem names for the metrics (required)
# application = "$NAMESPACE"
# subsystem = "$HOSTNAME"
## Additional OpenTelemetry resource attributes
# [outputs.opentelemetry.attributes]
# "service.name" = "demo"
## Additional gRPC request metadata
# [outputs.opentelemetry.headers]
# key1 = "value1"支持的方言
Coralogix
此插件通过取消注释 [output.opentelemetry.coralogix] 部分来支持将数据发送到 Coralogix 服务器。
在那里,您可以找到与服务器交互所需的设置。
private_key是您的私钥,您可以在Settings > Send Your Data中找到它。application是您的应用程序名称,它将被添加到您的metric attributes中。subsystem是您的子系统,它将被添加到您的 metric attributes 中。
更多信息请参阅 入门页面。
架构
InfluxDB->OpenTelemetry 转换 schema 和 实现 托管在 GitHub 上。
对于指标,存在两个输入 schema。测量名称为 prometheus 的行协议被假定具有与 Prometheus 输入插件匹配的 schema,当 metric_version = 2 时。其他测量名称的行协议被假定具有与 Prometheus 输入插件匹配的 schema,当 metric_version = 1 时。如果两个 schema 假设都失败,则行协议数据将被解释为
- Metric type = gauge (或 counter,如果输入插件指示)
- Metric name =
[measurement]_[field key] - Metric value = 行协议字段值,转换为 float
- Metric labels = 行协议 tags
另请参阅 OpenTelemetry 输入插件。
此页面是否有帮助?
感谢您的反馈!
支持和反馈
感谢您成为我们社区的一员!我们欢迎并鼓励您对 Telegraf 和本文档提出反馈和 bug 报告。要获取支持,请使用以下资源
具有年度合同或支持合同的客户可以 联系 InfluxData 支持。