目录
输入和输出集成概述
AMQP Consumer 输入插件允许您从兼容 AMQP 0-9-1 的消息代理(如 RabbitMQ)中摄取数据,从而实现无缝数据收集,用于监控和分析目的。
OpenTSDB 插件有助于 Telegraf 与 OpenTSDB 的集成,允许用户将时间序列指标无缝推送到 OpenTSDB 后端。
集成详情
AMQP
此插件为 AMQP 0-9-1 提供了一个消费者,RabbitMQ 是其一个突出的实现。AMQP(高级消息队列协议)最初是为了实现网络中不同系统之间可靠的、可互操作的消息传递而开发的。该插件使用配置的队列和绑定键从主题交换中读取指标,从而提供了一种灵活高效的方式来从兼容 AMQP 的消息传递系统中收集数据。这使用户能够利用现有的 RabbitMQ 实现来有效地监控其应用程序,通过捕获详细的指标进行分析和告警。
OpenTSDB
OpenTSDB 插件旨在通过 telnet 或 HTTP 模式将指标发送到 OpenTSDB 实例。随着 OpenTSDB 2.0 的推出,推荐的指标发送方法是通过 HTTP API,它允许通过配置“http_batch_size”来批量处理指标。该插件支持多个配置选项,包括指标前缀、服务器主机和端口规范、用于反向代理的 URI 路径自定义以及用于诊断与 OpenTSDB 通信问题的调试选项。此插件在生成时间序列数据并且需要高效存储在可扩展的时间序列数据库(如 OpenTSDB)中的场景中特别有用,使其适用于广泛的监控和分析应用。
配置
AMQP
[[inputs.amqp_consumer]]
## Brokers to consume from. If multiple brokers are specified a random broker
## will be selected anytime a connection is established. This can be
## helpful for load balancing when not using a dedicated load balancer.
brokers = ["amqp://localhost:5672/influxdb"]
## Authentication credentials for the PLAIN auth_method.
# username = ""
# password = ""
## Name of the exchange to declare. If unset, no exchange will be declared.
exchange = "telegraf"
## Exchange type; common types are "direct", "fanout", "topic", "header", "x-consistent-hash".
# exchange_type = "topic"
## If true, exchange will be passively declared.
# exchange_passive = false
## Exchange durability can be either "transient" or "durable".
# exchange_durability = "durable"
## Additional exchange arguments.
# exchange_arguments = { }
# exchange_arguments = {"hash_property" = "timestamp"}
## AMQP queue name.
queue = "telegraf"
## AMQP queue durability can be "transient" or "durable".
queue_durability = "durable"
## If true, queue will be passively declared.
# queue_passive = false
## Additional arguments when consuming from Queue
# queue_consume_arguments = { }
# queue_consume_arguments = {"x-stream-offset" = "first"}
## A binding between the exchange and queue using this binding key is
## created. If unset, no binding is created.
binding_key = "#"
## Maximum number of messages server should give to the worker.
# prefetch_count = 50
## Max undelivered messages
## This plugin uses tracking metrics, which ensure messages are read to
## outputs before acknowledging them to the original broker to ensure data
## is not lost. This option sets the maximum messages to read from the
## broker that have not been written by an output.
##
## This value needs to be picked with awareness of the agent's
## metric_batch_size value as well. Setting max undelivered messages too high
## can result in a constant stream of data batches to the output. While
## setting it too low may never flush the broker's messages.
# max_undelivered_messages = 1000
## Timeout for establishing the connection to a broker
# timeout = "30s"
## Auth method. PLAIN and EXTERNAL are supported
## Using EXTERNAL requires enabling the rabbitmq_auth_mechanism_ssl plugin as
## described here: https://rabbitmq.cn/plugins.html
# auth_method = "PLAIN"
## Optional TLS Config
# tls_ca = "/etc/telegraf/ca.pem"
# tls_cert = "/etc/telegraf/cert.pem"
# tls_key = "/etc/telegraf/key.pem"
## Use TLS but skip chain & host verification
# insecure_skip_verify = false
## Content encoding for message payloads, can be set to
## "gzip", "identity" or "auto"
## - Use "gzip" to decode gzip
## - Use "identity" to apply no encoding
## - Use "auto" determine the encoding using the ContentEncoding header
# content_encoding = "identity"
## Maximum size of decoded message.
## Acceptable units are B, KiB, KB, MiB, MB...
## Without quotes and units, interpreted as size in bytes.
# max_decompression_size = "500MB"
## 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"
OpenTSDB
[[outputs.opentsdb]]
## prefix for metrics keys
prefix = "my.specific.prefix."
## DNS name of the OpenTSDB server
## Using "opentsdb.example.com" or "tcp://opentsdb.example.com" will use the
## telnet API. "http://opentsdb.example.com" will use the Http API.
host = "opentsdb.example.com"
## Port of the OpenTSDB server
port = 4242
## Number of data points to send to OpenTSDB in Http requests.
## Not used with telnet API.
http_batch_size = 50
## URI Path for Http requests to OpenTSDB.
## Used in cases where OpenTSDB is located behind a reverse proxy.
http_path = "/api/put"
## Debug true - Prints OpenTSDB communication
debug = false
## Separator separates measurement name from field
separator = "_"
输入和输出集成示例
AMQP
-
集成应用指标与 AMQP:使用 AMQP Consumer 插件收集发布到 RabbitMQ 交换机的应用程序指标。通过配置插件以监听特定队列,团队可以深入了解应用程序性能,跟踪请求速率、错误计数和延迟指标,所有这些都是实时的。这种设置不仅有助于异常检测,还为容量规划和系统优化提供了有价值的数据。
-
事件驱动监控:每当应用程序内满足某些条件时,配置 AMQP Consumer 以触发特定的监控事件。例如,如果收到指示高错误率的消息,插件可以将此数据馈送到监控工具,生成警报或扩展事件。这种集成可以提高对问题的响应速度并自动化部分操作工作流程。
-
跨平台数据聚合:利用 AMQP Consumer 插件来整合来自分布在不同平台上的各种应用程序的指标。通过使用 RabbitMQ 作为集中式消息代理,组织可以统一其监控数据,从而通过 Telegraf 实现全面的分析和仪表板,从而在异构环境中保持可见性。
-
实时日志处理:扩展 AMQP Consumer 的用途,以捕获发送到 RabbitMQ 交换机的日志数据,实时处理日志以进行监控和告警。此应用确保通过分析日志模式、趋势和异常情况(在它们发生时)来快速检测和解决操作问题。
OpenTSDB
-
实时基础设施监控:利用 OpenTSDB 插件来收集和存储来自各种基础设施组件的指标。通过配置插件以将指标推送到 OpenTSDB,组织可以获得其基础设施健康状况和随时间推移的性能的集中视图。
-
自定义应用指标跟踪:将 OpenTSDB 插件集成到自定义应用程序中,以跟踪关键性能指标 (KPI),例如响应时间、错误率和用户交互。这种设置允许开发人员和产品团队可视化应用程序性能趋势并做出数据驱动的决策。
-
自动化异常检测:结合机器学习算法利用该插件来自动检测发送到 OpenTSDB 的时间序列数据中的异常。通过持续监控传入的指标,系统可以训练模型,在潜在问题影响应用程序性能之前向用户发出警报。
-
历史数据分析:使用 OpenTSDB 插件来存储和分析历史性能数据,用于容量规划和趋势分析。这提供了对系统随时间推移的行为的有价值的见解,帮助团队了解使用模式并为未来的增长做好准备。
反馈
感谢您成为我们社区的一份子!如果您有任何一般性反馈或在这些页面上发现了任何错误,我们欢迎并鼓励您提出意见。请在 InfluxDB 社区 Slack 中提交您的反馈。