目录
输入和输出集成概述
Syslog 插件支持使用标准网络协议从各种来源收集 syslog 消息。此功能对于需要有效监控和记录系统的环境至关重要。
此输出插件通过 HTTP 将指标从 Telegraf 直接流式传输到 ServiceNow MID Server,利用 nowmetric
序列化器与 ServiceNow 的 Operational Intelligence 和 Event Management 有效集成。
集成详情
Syslog
Telegraf 的 Syslog 插件捕获通过各种协议(如 TCP、UDP 和 TLS)传输的 syslog 消息。它支持 RFC 5424(较新的 syslog 协议)和较旧的 RFC 3164(BSD syslog 协议)。此插件作为服务输入运行,有效地启动一个服务来侦听传入的 syslog 消息。与传统插件不同,服务输入可能无法与标准间隔设置或 CLI 选项(如 --once
)一起使用。它包括用于设置网络配置、套接字权限、消息处理和连接处理的选项。此外,与 Rsyslog 的集成允许转发日志消息,使其成为实时收集和中继系统日志的强大工具,从而无缝集成到监控和日志记录系统中。
ServiceNow
Telegraf 可用于将指标数据直接发送到 ServiceNow MID Server REST 端点。指标使用 ServiceNow 的 Operational Intelligence (OI) 格式或 JSONv2 格式进行格式化,从而实现与 ServiceNow 的 Event Management 和 Operational Intelligence 平台的无缝集成。序列化器有效地批量处理指标,通过最大限度地减少 HTTP POST 请求的数量来降低网络开销。此集成使用户能够快速利用 ServiceNow 中的指标来增强可观察性、主动事件管理和性能监控,并利用 ServiceNow 的 Operational Intelligence 功能。
配置
Syslog
[[inputs.syslog]]
## Protocol, address and port to host the syslog receiver.
## If no host is specified, then localhost is used.
## If no port is specified, 6514 is used (RFC5425#section-4.1).
## ex: server = "tcp://localhost:6514"
## server = "udp://:6514"
## server = "unix:///var/run/telegraf-syslog.sock"
## When using tcp, consider using 'tcp4' or 'tcp6' to force the usage of IPv4
## or IPV6 respectively. There are cases, where when not specified, a system
## may force an IPv4 mapped IPv6 address.
server = "tcp://127.0.0.1:6514"
## Permission for unix sockets (only available on unix sockets)
## This setting may not be respected by some platforms. To safely restrict
## permissions it is recommended to place the socket into a previously
## created directory with the desired permissions.
## ex: socket_mode = "777"
# socket_mode = ""
## Maximum number of concurrent connections (only available on stream sockets like TCP)
## Zero means unlimited.
# max_connections = 0
## Read timeout (only available on stream sockets like TCP)
## Zero means unlimited.
# read_timeout = "0s"
## Optional TLS configuration (only available on stream sockets like TCP)
# tls_cert = "/etc/telegraf/cert.pem"
# tls_key = "/etc/telegraf/key.pem"
## Enables client authentication if set.
# tls_allowed_cacerts = ["/etc/telegraf/clientca.pem"]
## Maximum socket buffer size (in bytes when no unit specified)
## For stream sockets, once the buffer fills up, the sender will start
## backing up. For datagram sockets, once the buffer fills up, metrics will
## start dropping. Defaults to the OS default.
# read_buffer_size = "64KiB"
## Period between keep alive probes (only applies to TCP sockets)
## Zero disables keep alive probes. Defaults to the OS configuration.
# keep_alive_period = "5m"
## Content encoding for message payloads
## Can be set to "gzip" for compressed payloads or "identity" for no encoding.
# content_encoding = "identity"
## Maximum size of decoded packet (in bytes when no unit specified)
# max_decompression_size = "500MB"
## Framing technique used for messages transport
## Available settings are:
## octet-counting -- see RFC5425#section-4.3.1 and RFC6587#section-3.4.1
## non-transparent -- see RFC6587#section-3.4.2
# framing = "octet-counting"
## The trailer to be expected in case of non-transparent framing (default = "LF").
## Must be one of "LF", or "NUL".
# trailer = "LF"
## Whether to parse in best effort mode or not (default = false).
## By default best effort parsing is off.
# best_effort = false
## The RFC standard to use for message parsing
## By default RFC5424 is used. RFC3164 only supports UDP transport (no streaming support)
## Must be one of "RFC5424", or "RFC3164".
# syslog_standard = "RFC5424"
## Character to prepend to SD-PARAMs (default = "_").
## A syslog message can contain multiple parameters and multiple identifiers within structured data section.
## Eg., [id1 name1="val1" name2="val2"][id2 name1="val1" nameA="valA"]
## For each combination a field is created.
## Its name is created concatenating identifier, sdparam_separator, and parameter name.
# sdparam_separator = "_"
ServiceNow
[[outputs.http]]
## ServiceNow MID Server metrics endpoint
url = "http://mid-server.example.com:9082/api/mid/sa/metrics"
## HTTP request method
method = "POST"
## Basic Authentication credentials
username = "evt.integration"
password = "P@$$w0rd!"
## Data serialization format for ServiceNow
data_format = "nowmetric"
## Metric format type: "oi" (default) or "jsonv2"
nowmetric_format = "oi"
## HTTP Headers
[outputs.http.headers]
Content-Type = "application/json"
Accept = "application/json"
## Optional timeout
# timeout = "5s"
## TLS configuration options
# tls_ca = "/etc/telegraf/ca.pem"
# tls_cert = "/etc/telegraf/cert.pem"
# tls_key = "/etc/telegraf/key.pem"
# insecure_skip_verify = false
输入和输出集成示例
Syslog
-
集中式日志管理:使用 Syslog 插件将来自多台服务器的日志消息聚合到中央日志记录系统中。此设置可以通过收集来自不同来源的 syslog 数据,帮助监控整体系统运行状况、有效解决问题和维护审计跟踪。
-
实时警报:将 Syslog 插件与警报工具集成,以在检测到特定日志模式或错误时触发实时通知。例如,如果在日志中出现关键系统错误,则可以向运营团队发送警报,从而最大限度地减少停机时间并执行主动维护。
-
安全监控:通过捕获来自防火墙、入侵检测系统和其他安全设备的日志,利用 Syslog 插件进行安全监控。此日志记录功能增强了安全可见性,并通过分析捕获的 syslog 数据,帮助调查潜在的恶意活动。
-
应用程序性能跟踪:通过收集来自各种应用程序的日志,利用 Syslog 插件来监控应用程序性能。此集成有助于分析应用程序的行为和性能趋势,从而帮助优化应用程序流程并确保更流畅的运行。
ServiceNow
-
主动事件管理:利用 Telegraf 和 ServiceNow 集成将基础设施和应用程序指标实时流式传输到 ServiceNow Event Management。根据阈值自动触发事件或补救工作流程,从而显著缩短事件检测和响应时间。
-
端到端应用程序监控:在应用程序堆栈的多个层部署 Telegraf 代理,将性能指标直接发送到 ServiceNow。借助 ServiceNow 的 Operational Intelligence,团队可以将跨组件的指标关联起来,快速识别性能瓶颈。
-
动态 CI 性能跟踪:通过使用此插件推送性能数据,将 Telegraf 指标与 ServiceNow 的 CMDB 集成,从而允许根据实时指标自动更新配置项 (CI) 运行状况状态。这确保了 ServiceNow 中基础设施运行状况的准确和最新状态。
-
云资源优化:使用 Telegraf 从混合云和多云基础设施收集指标,直接流式传输到 ServiceNow。利用这些指标进行实时分析、预测性容量规划和资源优化,从而实现主动管理并降低运营成本。
反馈
感谢您成为我们社区的一份子!如果您对这些页面有任何一般性反馈或发现任何错误,我们欢迎并鼓励您提出意见。请在 InfluxDB 社区 Slack 中提交您的反馈。