目录
输入和输出集成概述
Docker 输入插件允许您使用 Docker Engine API 从 Docker 容器收集指标,从而增强容器化应用程序的可视性和监控。
此插件使 Telegraf 能够使用 InfluxDB 行协议将指标有效地直接写入 VictoriaMetrics,从而利用 VictoriaMetrics 的性能和可扩展性功能来处理大规模时序数据。
集成详情
Docker
Telegraf 的 Docker 输入插件从 Docker Engine API 收集有价值的指标,从而深入了解正在运行的容器。此插件利用官方 Docker 客户端与 Engine API 交互,允许用户监控各种容器状态、资源分配和性能指标。通过按名称和状态过滤容器的选项,以及可自定义的标签,此插件支持在各种环境中灵活监控容器化应用程序,无论是在本地系统上还是在 Kubernetes 等编排平台中。此外,它通过要求访问 Docker 守护进程的权限来解决安全问题,并强调在容器化环境中部署时进行正确的配置。
VictoriaMetrics
VictoriaMetrics 支持直接摄取 InfluxDB 行协议中的指标,这使得该插件非常适合高效的实时指标存储和检索。该集成将 Telegraf 广泛的指标收集功能与 VictoriaMetrics 优化的存储和查询功能相结合,包括压缩、快速摄取率和高效的磁盘利用率。该插件非常适合云原生和大规模监控场景,具有简单性、强大的性能和高可靠性,为大量指标提供高级操作洞察和长期存储解决方案。
配置
Docker
[[inputs.docker]]
## Docker Endpoint
## To use TCP, set endpoint = "tcp://[ip]:[port]"
## To use environment variables (ie, docker-machine), set endpoint = "ENV"
endpoint = "unix:///var/run/docker.sock"
## Set to true to collect Swarm metrics(desired_replicas, running_replicas)
## Note: configure this in one of the manager nodes in a Swarm cluster.
## configuring in multiple Swarm managers results in duplication of metrics.
gather_services = false
## Only collect metrics for these containers. Values will be appended to
## container_name_include.
## Deprecated (1.4.0), use container_name_include
container_names = []
## Set the source tag for the metrics to the container ID hostname, eg first 12 chars
source_tag = false
## Containers to include and exclude. Collect all if empty. Globs accepted.
container_name_include = []
container_name_exclude = []
## Container states to include and exclude. Globs accepted.
## When empty only containers in the "running" state will be captured.
# container_state_include = []
# container_state_exclude = []
## Objects to include for disk usage query
## Allowed values are "container", "image", "volume"
## When empty disk usage is excluded
storage_objects = []
## Timeout for docker list, info, and stats commands
timeout = "5s"
## Whether to report for each container per-device blkio (8:0, 8:1...),
## network (eth0, eth1, ...) and cpu (cpu0, cpu1, ...) stats or not.
## Usage of this setting is discouraged since it will be deprecated in favor of 'perdevice_include'.
## Default value is 'true' for backwards compatibility, please set it to 'false' so that 'perdevice_include' setting
## is honored.
perdevice = true
## Specifies for which classes a per-device metric should be issued
## Possible values are 'cpu' (cpu0, cpu1, ...), 'blkio' (8:0, 8:1, ...) and 'network' (eth0, eth1, ...)
## Please note that this setting has no effect if 'perdevice' is set to 'true'
# perdevice_include = ["cpu"]
## Whether to report for each container total blkio and network stats or not.
## Usage of this setting is discouraged since it will be deprecated in favor of 'total_include'.
## Default value is 'false' for backwards compatibility, please set it to 'true' so that 'total_include' setting
## is honored.
total = false
## Specifies for which classes a total metric should be issued. Total is an aggregated of the 'perdevice' values.
## Possible values are 'cpu', 'blkio' and 'network'
## Total 'cpu' is reported directly by Docker daemon, and 'network' and 'blkio' totals are aggregated by this plugin.
## Please note that this setting has no effect if 'total' is set to 'false'
# total_include = ["cpu", "blkio", "network"]
## docker labels to include and exclude as tags. Globs accepted.
## Note that an empty array for both will include all labels as tags
docker_label_include = []
docker_label_exclude = []
## Which environment variables should we use as a tag
tag_env = ["JAVA_HOME", "HEAP_SIZE"]
## 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
VictoriaMetrics
[[outputs.influxdb]]
## URL of the VictoriaMetrics write endpoint
urls = ["http://localhost:8428"]
## VictoriaMetrics accepts InfluxDB line protocol directly
database = "db_name"
## Optional authentication
# username = "username"
# password = "password"
# skip_database_creation = true
# exclude_retention_policy_tag = true
# content_encoding = "gzip"
## Timeout for HTTP requests
timeout = "5s"
## Optional TLS configuration
# tls_ca = "/path/to/ca.pem"
# tls_cert = "/path/to/cert.pem"
# tls_key = "/path/to/key.pem"
# insecure_skip_verify = false
输入和输出集成示例
Docker
-
监控容器化应用程序的性能:使用 Docker 输入插件来跟踪 Docker 容器中运行的应用程序的 CPU、内存、磁盘 I/O 和网络活动。通过收集这些指标,DevOps 团队可以主动管理资源分配、排除性能瓶颈并确保跨不同环境的最佳应用程序性能。
-
与 Kubernetes 集成:利用此插件从 Kubernetes 编排的 Docker 容器收集指标。通过过滤掉不必要的 Kubernetes 标签并专注于关键指标,团队可以简化其监控解决方案并创建仪表板,以深入了解 Kubernetes 集群中运行的微服务的整体运行状况。
-
容量规划和资源优化:使用 Docker 输入插件收集的指标来执行 Docker 部署的容量规划。分析使用模式有助于识别未充分利用的资源和过度配置的容器,从而指导根据实际使用趋势扩展或缩减规模的决策。
-
容器异常的自动警报:根据通过 Docker 插件收集的指标设置警报规则,以通知团队资源使用量或服务中断异常激增。这种主动监控方法有助于保持服务可靠性并优化容器化应用程序的性能。
VictoriaMetrics
-
云原生应用程序监控:将 Kubernetes 上部署的微服务的指标直接流式传输到 VictoriaMetrics。通过集中指标,组织可以在动态发展的云环境中执行实时监控、快速异常检测和无缝可扩展性。
-
可扩展的物联网数据管理:使用该插件将来自物联网部署的传感器数据摄取到 VictoriaMetrics。这种方法有助于实时分析、预测性维护以及以最小的存储开销有效管理海量传感器数据。
-
金融系统性能跟踪:通过此插件利用 VictoriaMetrics 来存储和分析来自金融系统的指标,捕获延迟、交易量和错误率。组织可以快速识别和解决性能瓶颈,从而确保高可用性和法规遵从性。
-
跨环境性能仪表板:将来自各种基础设施组件(例如云实例、容器和物理服务器)的指标集成到 VictoriaMetrics 中。使用可视化工具,团队可以构建全面的仪表板,以实现端到端性能可见性、主动故障排除和基础设施优化。
反馈
感谢您成为我们社区的一份子!如果您有任何一般性反馈或在这些页面上发现任何错误,我们欢迎并鼓励您提供意见。请在 InfluxDB 社区 Slack 中提交您的反馈。