目录
强大的性能，无限的扩展
收集、组织和处理海量高速数据。 当您将其视为时序数据时，任何数据都更有价值。 使用 InfluxDB，这个排名第一的时序平台旨在通过 Telegraf 进行扩展。
查看入门方法
输入和输出集成概述
OPC UA 插件提供了一个接口，用于从 OPC UA 服务器设备检索数据，从而促进有效的数据收集和监控。
Loki 插件允许用户将日志发送到 Loki 进行聚合和查询，从而利用 Loki 高效的存储功能。
集成详情
OPC UA
OPC UA 插件从使用 OPC UA 协议通信的设备检索数据，允许您从 OPC UA 服务器收集和监控数据。
Loki
此 Loki 插件与 Grafana Loki 集成，这是一个强大的日志聚合系统。 通过以与 Loki 兼容的格式发送日志，此插件可以高效地存储和查询日志。 每个日志条目都以键值格式结构化，其中键表示字段名称，值表示相应的日志信息。 按时间戳对日志进行排序可确保通过 Loki 查询时，日志流保持时间顺序。 此插件对密钥的支持使安全管理身份验证参数变得更加容易，而 HTTP 标头、gzip 编码和 TLS 配置的选项增强了日志传输的适应性和安全性，满足了各种部署需求。
配置
OPC UA
[[inputs.opcua]]
## Metric name
# name = "opcua"
#
## OPC UA Endpoint URL
# endpoint = "opc.tcp://localhost:4840"
#
## Maximum time allowed to establish a connect to the endpoint.
# connect_timeout = "10s"
#
## Maximum time allowed for a request over the established connection.
# request_timeout = "5s"
# Maximum time that a session shall remain open without activity.
# session_timeout = "20m"
#
## Security policy, one of "None", "Basic128Rsa15", "Basic256",
## "Basic256Sha256", or "auto"
# security_policy = "auto"
#
## Security mode, one of "None", "Sign", "SignAndEncrypt", or "auto"
# security_mode = "auto"
#
## Path to cert.pem. Required when security mode or policy isn't "None".
## If cert path is not supplied, self-signed cert and key will be generated.
# certificate = "/etc/telegraf/cert.pem"
#
## Path to private key.pem. Required when security mode or policy isn't "None".
## If key path is not supplied, self-signed cert and key will be generated.
# private_key = "/etc/telegraf/key.pem"
#
## Authentication Method, one of "Certificate", "UserName", or "Anonymous". To
## authenticate using a specific ID, select 'Certificate' or 'UserName'
# auth_method = "Anonymous"
#
## Username. Required for auth_method = "UserName"
# username = ""
#
## Password. Required for auth_method = "UserName"
# password = ""
#
## Option to select the metric timestamp to use. Valid options are:
## "gather" -- uses the time of receiving the data in telegraf
## "server" -- uses the timestamp provided by the server
## "source" -- uses the timestamp provided by the source
# timestamp = "gather"
#
## Client trace messages
## When set to true, and debug mode enabled in the agent settings, the OPCUA
## client's messages are included in telegraf logs. These messages are very
## noisey, but essential for debugging issues.
# client_trace = false
#
## Include additional Fields in each metric
## Available options are:
## DataType -- OPC-UA Data Type (string)
# optional_fields = []
#
## Node ID configuration
## name - field name to use in the output
## namespace - OPC UA namespace of the node (integer value 0 thru 3)
## identifier_type - OPC UA ID type (s=string, i=numeric, g=guid, b=opaque)
## identifier - OPC UA ID (tag as shown in opcua browser)
## tags - extra tags to be added to the output metric (optional); deprecated in 1.25.0; use default_tags
## default_tags - extra tags to be added to the output metric (optional)
##
## Use either the inline notation or the bracketed notation, not both.
#
## Inline notation (default_tags not supported yet)
# nodes = [
# {name="", namespace="", identifier_type="", identifier="", tags=[["tag1", "value1"], ["tag2", "value2"]},
# {name="", namespace="", identifier_type="", identifier=""},
# ]
#
## Bracketed notation
# [[inputs.opcua.nodes]]
# name = "node1"
# namespace = ""
# identifier_type = ""
# identifier = ""
# default_tags = { tag1 = "value1", tag2 = "value2" }
#
# [[inputs.opcua.nodes]]
# name = "node2"
# namespace = ""
# identifier_type = ""
# identifier = ""
#
## Node Group
## Sets defaults so they aren't required in every node.
## Default values can be set for:
## * Metric name
## * OPC UA namespace
## * Identifier
## * Default tags
##
## Multiple node groups are allowed
#[[inputs.opcua.group]]
## Group Metric name. Overrides the top level name. If unset, the
## top level name is used.
# name =
#
## Group default namespace. If a node in the group doesn't set its
## namespace, this is used.
# namespace =
#
## Group default identifier type. If a node in the group doesn't set its
## namespace, this is used.
# identifier_type =
#
## Default tags that are applied to every node in this group. Can be
## overwritten in a node by setting a different value for the tag name.
## example: default_tags = { tag1 = "value1" }
# default_tags = {}
#
## Node ID Configuration. Array of nodes with the same settings as above.
## Use either the inline notation or the bracketed notation, not both.
#
## Inline notation (default_tags not supported yet)
# nodes = [
# {name="node1", namespace="", identifier_type="", identifier=""},
# {name="node2", namespace="", identifier_type="", identifier=""},
#]
#
## Bracketed notation
# [[inputs.opcua.group.nodes]]
# name = "node1"
# namespace = ""
# identifier_type = ""
# identifier = ""
# default_tags = { tag1 = "override1", tag2 = "value2" }
#
# [[inputs.opcua.group.nodes]]
# name = "node2"
# namespace = ""
# identifier_type = ""
# identifier = ""
## Enable workarounds required by some devices to work correctly
# [inputs.opcua.workarounds]
## Set additional valid status codes, StatusOK (0x0) is always considered valid
# additional_valid_status_codes = ["0xC0"]
# [inputs.opcua.request_workarounds]
## Use unregistered reads instead of registered reads
# use_unregistered_reads = false
Loki
[[outputs.loki]]
## The domain of Loki
domain = "https://loki.domain.tld"
## Endpoint to write api
# endpoint = "/loki/api/v1/push"
## Connection timeout, defaults to "5s" if not set.
# timeout = "5s"
## Basic auth credential
# username = "loki"
# password = "pass"
## Additional HTTP headers
# http_headers = {"X-Scope-OrgID" = "1"}
## If the request must be gzip encoded
# gzip_request = false
## Optional TLS Config
# tls_ca = "/etc/telegraf/ca.pem"
# tls_cert = "/etc/telegraf/cert.pem"
# tls_key = "/etc/telegraf/key.pem"
## Sanitize Tag Names
## If true, all tag names will have invalid characters replaced with
## underscores that do not match the regex: ^[a-zA-Z_:][a-zA-Z0-9_:]*.
# sanitize_label_names = false
## Metric Name Label
## Label to use for the metric name to when sending metrics. If set to an
## empty string, this will not add the label. This is NOT suggested as there
## is no way to differentiate between multiple metrics.
# metric_name_label = "__name"
输入和输出集成示例
OPC UA
-
基本配置：使用 OPC UA 服务器端点和所需的指标设置插件。 这允许 Telegraf 开始从配置的节点收集指标。
-
节点 ID 设置：使用配置指定特定节点（例如温度传感器）以实时监控其值。 例如，配置节点
ns=3;s=Temperature以直接收集温度数据。 -
组配置：通过将多个节点分组到一个配置下，简化对多个节点的监控——这将为该组中的所有节点设置默认值，从而减少设置中的冗余。
Loki
-
微服务集中日志记录：利用 Loki 插件收集在 Kubernetes 集群中运行的多个微服务的日志。 通过将日志定向到集中的 Loki 实例，开发人员可以在一个地方监控、搜索和分析来自所有服务的日志，从而更轻松地进行故障排除和性能监控。 此设置简化了操作，并支持对分布式应用程序中出现的问题做出快速响应。
-
实时日志异常检测：将 Loki 与监控工具结合使用，以实时分析日志输出中可能表明系统错误或安全威胁的异常模式。 在日志流上实施异常检测使团队能够主动识别和响应事件，从而提高系统可靠性并增强安全态势。
-
使用 Gzip 压缩增强日志处理：配置 Loki 插件以使用 gzip 压缩进行日志传输。 这种方法可以减少带宽使用并提高传输速度，尤其是在网络带宽可能受到限制的环境中非常有利。 它对于每个字节都很重要且性能至关重要的大容量日志记录应用程序特别有用。
-
使用自定义标头进行多租户支持：利用添加自定义 HTTP 标头的功能来隔离多租户应用程序环境中来自不同租户的日志。 通过使用 Loki 插件为每个租户发送不同的标头，运营商可以确保正确的日志管理并符合数据隔离要求，使其成为 SaaS 应用程序的通用解决方案。
反馈
感谢您成为我们社区的一员！ 如果您有任何一般性反馈或在这些页面上发现任何错误，我们欢迎并鼓励您提供意见。 请在 InfluxDB 社区 Slack 中提交您的反馈。
强大的性能，无限的扩展
收集、组织和处理海量高速数据。 当您将其视为时序数据时，任何数据都更有价值。 使用 InfluxDB，这个排名第一的时序平台旨在通过 Telegraf 进行扩展。
查看入门方法
