目录
强大的性能,无限的扩展能力
收集、组织和处理海量高速数据。 当您将任何数据视为时间序列数据时,它会更有价值。 借助 InfluxDB,第一的时间序列平台,旨在与 Telegraf 一起扩展。
查看入门方法
输入和输出集成概述
此插件从必要的 OpenStack 服务收集指标,从而促进云基础设施的监控和管理。
AWS Timestream Telegraf 插件使用户能够将指标直接发送到 Amazon 的 Timestream 服务,该服务专为时间序列数据管理而设计。 该插件为身份验证、数据组织和保留设置提供了各种配置选项。
集成详情
OpenStack
OpenStack 插件允许用户从各种 OpenStack 服务(如 CINDER、GLANCE、HEAT、KEYSTONE、NEUTRON 和 NOVA)收集性能指标。 它支持多个 OpenStack API 来获取与这些服务相关的关键指标,从而实现对云资源的全面监控和管理。 随着组织越来越多地采用 OpenStack 作为其云基础设施,此插件在提供对整个云环境中的资源使用、可用性和性能的洞察方面发挥着至关重要的作用。 配置选项允许自定义轮询间隔和过滤不需要的标签,以优化性能和基数。
AWS Timestream
此插件旨在高效地将指标写入 Amazon 的 Timestream 服务,这是一种针对物联网和运营应用程序优化的时间序列数据库。 借助此插件,Telegraf 可以发送从各种来源收集的数据,并支持身份验证、数据组织和保留管理的灵活配置。 它使用凭证链进行身份验证,允许各种方法,如 Web 身份、承担角色和共享配置文件。 用户可以定义指标在 Timestream 中的组织方式 - 是使用单个表还是多个表,以及对磁存储和内存存储保留期等方面的控制。 一个关键特性是它能够处理多测量记录,从而实现高效的数据摄取,并有助于减少多次写入的开销。 在错误处理方面,该插件包含用于解决数据写入期间与 AWS 错误相关的常见问题的机制,例如用于节流的重试逻辑以及根据需要创建表的能力。
配置
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
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
##
输入和输出集成示例
OpenStack
-
跨云管理:利用 OpenStack 插件从单个 Telegraf 实例监控和管理多个 OpenStack 云。 通过聚合不同云的指标,组织可以深入了解资源利用率,并优化其云架构以实现成本和性能。
-
基于指标的自动扩展:将从 OpenStack 收集的指标集成到自动扩展解决方案中。 例如,如果插件检测到特定服务的性能下降,它可以触发自动扩展规则以启动其他实例,确保系统性能在不同的工作负载下保持最佳状态。
-
性能监控仪表板:使用 OpenStack Telegraf 插件收集的数据来支持实时监控仪表板。 此设置提供了来自 OpenStack 服务的关键指标的可视化,使利益相关者能够快速识别趋势、查明问题,并在管理其云基础设施时做出数据驱动的决策。
-
服务可用性报告和分析:通过利用从各种 OpenStack 服务收集的指标,团队可以生成关于服务可用性和随时间变化的性能的详细报告。 此信息可以帮助识别重复出现的问题、改进服务交付,并就基础设施或服务配置的更改做出明智的决策。
AWS Timestream
-
物联网数据指标:使用 Timestream 插件将来自物联网设备的实时指标发送到 Timestream,从而可以快速分析和可视化传感器数据。 通过将设备读数组织成时间序列格式,用户可以跟踪趋势、识别异常,并根据设备性能简化运营决策。
-
应用程序性能监控:将 Timestream 与应用程序监控工具结合使用,以发送关于服务性能随时间变化的指标。 这种集成使工程师能够对应用程序性能进行历史分析,将其与业务指标相关联,并根据随时间推移查看的使用模式优化资源分配。
-
自动数据归档:配置 Timestream 插件以将数据写入 Timestream,同时管理保留期。 此设置可以自动执行归档策略,确保根据预定义的标准保留旧数据。 这对于合规性和历史分析特别有用,使企业能够以最少的人工干预来维护其数据生命周期。
-
多应用程序指标聚合:利用 Timestream 插件将来自多个应用程序的指标聚合到 Timestream 中。 通过创建性能指标的统一数据库,组织可以深入了解各种服务,提高对全系统性能的可见性,并促进跨应用程序故障排除。
反馈
感谢您成为我们社区的一份子! 如果您有任何一般性反馈或在这些页面上发现任何错误,我们欢迎并鼓励您提出意见。 请在 InfluxDB 社区 Slack 中提交您的反馈。
强大的性能,无限的扩展能力
收集、组织和处理海量高速数据。 当您将任何数据视为时间序列数据时,它会更有价值。 借助 InfluxDB,第一的时间序列平台,旨在与 Telegraf 一起扩展。
查看入门方法