目录
输入和输出集成概述
Telegraf 的 Ceph 插件有助于从 Ceph 存储集群中的 MON 和 OSD 节点收集性能指标,以实现有效的监控和管理。
AWS Timestream Telegraf 插件使用户能够将指标直接发送到 Amazon 的 Timestream 服务,该服务专为时间序列数据管理而设计。此插件提供各种配置选项,用于身份验证、数据组织和保留设置。
集成详情
Ceph
Ceph Storage Telegraf 插件旨在从 Ceph 存储集群中的 Monitor (MON) 和 Object Storage Daemon (OSD) 节点收集性能指标。Ceph 是一种高度可扩展的存储系统,通过此插件集成了其指标收集,从而方便地监控其组件。随着此插件在 13.x Mimic 版本中的引入,用户可以有效地收集有关其 Ceph 基础设施的性能和运行状况的详细见解。它的工作原理是扫描配置的套接字目录以查找特定的 Ceph 服务套接字文件,通过 Ceph 管理界面执行命令,并解析返回的 JSON 数据以获取指标。指标基于顶级键进行组织,从而可以有效地监控和分析集群性能。此插件通过允许管理员了解系统行为并主动识别潜在问题,为管理和维护 Ceph 集群的性能提供了有价值的功能。
AWS Timestream
此插件旨在高效地将指标写入 Amazon 的 Timestream 服务,Timestream 服务是一个针对物联网和运营应用程序优化的时间序列数据库。借助此插件,Telegraf 可以发送从各种来源收集的数据,并支持灵活的配置,用于身份验证、数据组织和保留管理。它利用凭证链进行身份验证,允许各种方法,例如 Web 身份、承担角色和共享配置文件。用户可以定义指标在 Timestream 中的组织方式 - 是使用单个表还是多个表,以及控制磁存储和内存存储的保留期等各个方面。一个关键功能是它能够处理多指标记录,从而实现高效的数据摄取,并有助于减少多次写入的开销。在错误处理方面,该插件包括用于解决数据写入期间与 AWS 错误相关的常见问题的机制,例如用于节流的重试逻辑以及根据需要创建表的功能。
配置
Ceph
[[inputs.ceph]]
## This is the recommended interval to poll. Too frequent and you
## will lose data points due to timeouts during rebalancing and recovery
interval = '1m'
## All configuration values are optional, defaults are shown below
## location of ceph binary
ceph_binary = "/usr/bin/ceph"
## directory in which to look for socket files
socket_dir = "/var/run/ceph"
## prefix of MON and OSD socket files, used to determine socket type
mon_prefix = "ceph-mon"
osd_prefix = "ceph-osd"
mds_prefix = "ceph-mds"
rgw_prefix = "ceph-client"
## suffix used to identify socket files
socket_suffix = "asok"
## Ceph user to authenticate as, ceph will search for the corresponding
## keyring e.g. client.admin.keyring in /etc/ceph, or the explicit path
## defined in the client section of ceph.conf for example:
##
## [client.telegraf]
## keyring = /etc/ceph/client.telegraf.keyring
##
## Consult the ceph documentation for more detail on keyring generation.
ceph_user = "client.admin"
## Ceph configuration to use to locate the cluster
ceph_config = "/etc/ceph/ceph.conf"
## Whether to gather statistics via the admin socket
gather_admin_socket_stats = true
## Whether to gather statistics via ceph commands, requires ceph_user
## and ceph_config to be specified
gather_cluster_stats = false
AWS Timestream
[[outputs.timestream]]
## Amazon Region
region = "us-east-1"
## Amazon Credentials
## Credentials are loaded in the following order:
## 1) Web identity provider credentials via STS if role_arn and web_identity_token_file are specified
## 2) Assumed credentials via STS if role_arn is specified
## 3) explicit credentials from 'access_key' and 'secret_key'
## 4) shared profile from 'profile'
## 5) environment variables
## 6) shared credentials file
## 7) EC2 Instance Profile
#access_key = ""
#secret_key = ""
#token = ""
#role_arn = ""
#web_identity_token_file = ""
#role_session_name = ""
#profile = ""
#shared_credential_file = ""
## Endpoint to make request against, the correct endpoint is automatically
## determined and this option should only be set if you wish to override the
## default.
## ex: endpoint_url = "http://localhost:8000"
# endpoint_url = ""
## Timestream database where the metrics will be inserted.
## The database must exist prior to starting Telegraf.
database_name = "yourDatabaseNameHere"
## Specifies if the plugin should describe the Timestream database upon starting
## to validate if it has access necessary permissions, connection, etc., as a safety check.
## If the describe operation fails, the plugin will not start
## and therefore the Telegraf agent will not start.
describe_database_on_start = false
## Specifies how the data is organized in Timestream.
## Valid values are: single-table, multi-table.
## When mapping_mode is set to single-table, all of the data is stored in a single table.
## When mapping_mode is set to multi-table, the data is organized and stored in multiple tables.
## The default is multi-table.
mapping_mode = "multi-table"
## Specifies if the plugin should create the table, if the table does not exist.
create_table_if_not_exists = true
## Specifies the Timestream table magnetic store retention period in days.
## Check Timestream documentation for more details.
## NOTE: This property is valid when create_table_if_not_exists = true.
create_table_magnetic_store_retention_period_in_days = 365
## Specifies the Timestream table memory store retention period in hours.
## Check Timestream documentation for more details.
## NOTE: This property is valid when create_table_if_not_exists = true.
create_table_memory_store_retention_period_in_hours = 24
## Specifies how the data is written into Timestream.
## Valid values are: true, false
## When use_multi_measure_records is set to true, all of the tags and fields are stored
## as a single row in a Timestream table.
## When use_multi_measure_record is set to false, Timestream stores each field in a
## separate table row, thereby storing the tags multiple times (once for each field).
## The recommended setting is true.
## The default is false.
use_multi_measure_records = "false"
## Specifies the measure_name to use when sending multi-measure records.
## NOTE: This property is valid when use_multi_measure_records=true and mapping_mode=multi-table
measure_name_for_multi_measure_records = "telegraf_measure"
## Specifies the name of the table to write data into
## NOTE: This property is valid when mapping_mode=single-table.
# single_table_name = ""
## Specifies the name of dimension when all of the data is being stored in a single table
## and the measurement name is transformed into the dimension value
## (see Mapping data from Influx to Timestream for details)
## NOTE: This property is valid when mapping_mode=single-table.
# single_table_dimension_name_for_telegraf_measurement_name = "namespace"
## Only valid and optional if create_table_if_not_exists = true
## Specifies the Timestream table tags.
## Check Timestream documentation for more details
# create_table_tags = { "foo" = "bar", "environment" = "dev"}
## Specify the maximum number of parallel go routines to ingest/write data
## If not specified, defaulted to 1 go routines
max_write_go_routines = 25
## Please see README.md to know how line protocol data is mapped to Timestream
##
输入和输出集成示例
Ceph
-
动态监控仪表板:利用 Ceph 插件创建实时监控仪表板,以可视化方式呈现 Ceph 集群的性能指标。通过将这些指标集成到集中式仪表板中,系统管理员可以立即深入了解存储基础设施的运行状况,这有助于在潜在问题升级之前快速识别和解决它们。
-
自动化警报系统:实施 Ceph 插件并结合警报解决方案,以自动通知管理员 Ceph 集群内的性能下降或运营问题。通过定义关键指标的阈值,组织可以确保及时的响应措施,从而提高整体系统可靠性和性能。
-
性能基准测试:使用此插件收集的指标对 Ceph 存储集群的不同配置或硬件设置进行性能基准测试。此过程可以帮助组织识别可提高性能和资源利用率的最佳配置,从而促进更高效的存储环境。
-
容量规划和预测:将从 Ceph 存储插件收集的指标集成到更广泛的数据分析和报告工具中,以促进容量规划。通过分析历史指标,组织可以预测未来的利用率趋势,从而为有效扩展存储资源做出明智的决策。
AWS Timestream
-
物联网数据指标:使用 Timestream 插件将来自物联网设备的实时指标发送到 Timestream,从而可以快速分析和可视化传感器数据。通过将设备读数组织成时间序列格式,用户可以跟踪趋势、识别异常并根据设备性能简化运营决策。
-
应用程序性能监控:将 Timestream 与应用程序监控工具结合使用,以随时间推移发送有关服务性能的指标。此集成使工程师能够对应用程序性能进行历史分析,将其与业务指标相关联,并根据随时间推移的使用模式优化资源分配。
-
自动化数据归档:配置 Timestream 插件以将数据写入 Timestream,同时管理保留期。此设置可以自动化归档策略,确保根据预定义的标准保留较旧的数据。这对于合规性和历史分析尤其有用,使企业能够以最少的人工干预来维护其数据生命周期。
-
多应用程序指标聚合:利用 Timestream 插件将来自多个应用程序的指标聚合到 Timestream 中。通过创建统一的性能指标数据库,组织可以全面了解各种服务,提高系统级性能的可见性,并促进跨应用程序故障排除。
反馈
感谢您成为我们社区的一份子!如果您有任何一般反馈或在这些页面上发现了任何错误,我们欢迎并鼓励您提出意见。请在 InfluxDB 社区 Slack 中提交您的反馈。