目录
输入和输出集成概述
此插件从必要的 OpenStack 服务收集指标,从而促进云基础设施的监控和管理。
Graphite 插件使用户能够通过 TCP 将 Telegraf 收集的指标发送到 Graphite。这种集成允许使用 Graphite 的强大功能高效地存储和可视化时间序列数据。
集成详情
OpenStack
OpenStack 插件允许用户从各种 OpenStack 服务(如 CINDER、GLANCE、HEAT、KEYSTONE、NEUTRON 和 NOVA)收集性能指标。它支持多个 OpenStack API 来获取与这些服务相关的关键指标,从而实现对云资源的全面监控和管理。随着组织越来越多地采用 OpenStack 作为其云基础设施,此插件在提供对整个云环境中的资源使用、可用性和性能的洞察方面发挥着至关重要的作用。配置选项允许自定义轮询间隔和过滤不需要的标签,以优化性能和基数。
Graphite
此插件通过原始 TCP 将指标写入 Graphite,从而将 Telegraf 收集的指标无缝集成到 Graphite 生态系统中。借助此插件,用户可以配置多个 TCP 端点以进行负载平衡,从而确保指标传输的高可用性和可靠性。使用前缀自定义指标命名以及利用各种模板选项的功能增强了数据在 Graphite 中表示方式的灵活性。此外,对 Graphite 标签的支持以及对指标名称进行严格清理的选项允许进行强大的数据管理,以满足用户的不同需求。对于希望利用 Graphite 强大的指标存储和可视化功能,同时保持对数据表示的控制的组织来说,此功能至关重要。
配置
OpenStack
[[inputs.openstack]]
## The recommended interval to poll is '30m'
## The identity endpoint to authenticate against and get the service catalog from.
authentication_endpoint = "https://my.openstack.cloud:5000"
## The domain to authenticate against when using a V3 identity endpoint.
# domain = "default"
## The project to authenticate as.
# project = "admin"
## User authentication credentials. Must have admin rights.
username = "admin"
password = "password"
## Available services are:
## "agents", "aggregates", "cinder_services", "flavors", "hypervisors",
## "networks", "nova_services", "ports", "projects", "servers",
## "serverdiagnostics", "services", "stacks", "storage_pools", "subnets",
## "volumes"
# enabled_services = ["services", "projects", "hypervisors", "flavors", "networks", "volumes"]
## Query all instances of all tenants for the volumes and server services
## NOTE: Usually this is only permitted for administrators!
# query_all_tenants = true
## output secrets (such as adminPass(for server) and UserID(for volume)).
# output_secrets = false
## Amount of time allowed to complete the HTTP(s) request.
# timeout = "5s"
## HTTP Proxy support
# http_proxy_url = ""
## Optional TLS Config
# tls_ca = /path/to/cafile
# tls_cert = /path/to/certfile
# tls_key = /path/to/keyfile
## Use TLS but skip chain & host verification
# insecure_skip_verify = false
## Options for tags received from Openstack
# tag_prefix = "openstack_tag_"
# tag_value = "true"
## Timestamp format for timestamp data received from Openstack.
## If false format is unix nanoseconds.
# human_readable_timestamps = false
## Measure Openstack call duration
# measure_openstack_requests = false
Graphite
# Configuration for Graphite server to send metrics to
[[outputs.graphite]]
## TCP endpoint for your graphite instance.
## If multiple endpoints are configured, the output will be load balanced.
## Only one of the endpoints will be written to with each iteration.
servers = ["localhost:2003"]
## Local address to bind when connecting to the server
## If empty or not set, the local address is automatically chosen.
# local_address = ""
## Prefix metrics name
prefix = ""
## Graphite output template
## see https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
template = "host.tags.measurement.field"
## Strict sanitization regex
## This is the default sanitization regex that is used on data passed to the
## graphite serializer. Users can add additional characters here if required.
## Be aware that the characters, '/' '@' '*' are always replaced with '_',
## '..' is replaced with '.', and '\' is removed even if added to the
## following regex.
# graphite_strict_sanitize_regex = '[^a-zA-Z0-9-:._=\p{L}]'
## Enable Graphite tags support
# graphite_tag_support = false
## Applied sanitization mode when graphite tag support is enabled.
## * strict - uses the regex specified above
## * compatible - allows for greater number of characters
# graphite_tag_sanitize_mode = "strict"
## Character for separating metric name and field for Graphite tags
# graphite_separator = "."
## Graphite templates patterns
## 1. Template for cpu
## 2. Template for disk*
## 3. Default template
# templates = [
# "cpu tags.measurement.host.field",
# "disk* measurement.field",
# "host.measurement.tags.field"
#]
## timeout in seconds for the write connection to graphite
# timeout = "2s"
## 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
输入和输出集成示例
OpenStack
-
跨云管理:利用 OpenStack 插件从单个 Telegraf 实例监控和管理多个 OpenStack 云。通过聚合不同云的指标,组织可以深入了解资源利用率,并优化其云架构以实现成本和性能的优化。
-
基于指标的自动扩展:将从 OpenStack 收集的指标集成到自动扩展解决方案中。例如,如果插件检测到特定服务的性能下降,它可以触发自动扩展规则以启动额外的实例,从而确保系统性能在不同的工作负载下保持最佳状态。
-
性能监控仪表板:使用 OpenStack Telegraf 插件收集的数据为实时监控仪表板提供支持。此设置提供来自 OpenStack 服务的关键指标的可视化,使利益干系人能够快速识别趋势、查明问题,并在管理其云基础设施时做出数据驱动的决策。
-
服务可用性报告和分析:通过利用从各种 OpenStack 服务收集的指标,团队可以生成关于服务可用性和随时间变化的性能的详细报告。此信息可以帮助识别重复出现的问题,改进服务交付,并就基础设施或服务配置的更改做出明智的决策。
Graphite
-
动态指标可视化:Graphite 插件可用于将来自各种来源(例如应用程序性能数据或服务器运行状况指标)的实时指标馈送到 Graphite 中。这种动态集成允许团队创建交互式仪表板,可视化关键绩效指标,跟踪随时间变化的趋势,并做出数据驱动的决策以增强系统性能。
-
负载均衡指标收集:通过在插件中配置多个 TCP 端点,组织可以实现指标传输的负载均衡。此用例确保指标交付既具有弹性又高效,从而降低了高流量期间数据丢失的风险,并保持了向 Graphite 的可靠信息流。
-
自定义指标标记:凭借对 Graphite 标签的支持,用户可以利用 Graphite 插件来增强其指标的粒度。使用相关信息(例如应用程序环境或服务类型)标记指标,可以进行更精细的查询和分析,从而使团队能够深入研究特定感兴趣的领域,以获得更好的运营洞察力。
-
增强的数据清理:利用插件的严格清理选项,用户可以确保其指标名称符合 Graphite 的要求。这种主动措施消除了指标名称中无效字符引起的潜在问题,从而实现了更清洁的数据管理和更准确的可视化。
反馈
感谢您成为我们社区的一份子!如果您有任何一般性反馈或在这些页面上发现任何错误,我们欢迎并鼓励您提出意见。请在 InfluxDB 社区 Slack 中提交您的反馈。