目录
输入和输出集成概述
此插件报告 Suricata IDS/IPS 引擎的内部性能计数器,并处理传入数据以适应 Telegraf 的格式。
此插件使用参数化的 SQL INSERT 语句将来自 Telegraf 的指标直接写入 MariaDB,提供了一种将指标存储在结构化关系表中的灵活方式。
集成详情
Suricata
Suricata 插件捕获并报告来自 Suricata IDS/IPS 引擎的内部性能指标,其中包括各种统计信息,如流量、内存使用率、正常运行时间以及流和警报的计数器。此插件监听来自 Suricata 的 JSON 格式日志输出,使其能够解析和格式化数据以与 Telegraf 集成。它作为服务输入插件运行,意味着它主动等待来自 Suricata 的指标或事件,而不是以预定义的间隔收集指标。该插件支持不同指标版本的配置,从而提高了灵活性和详细的数据收集。
MariaDB
Telegraf 中的 SQL 输出插件通过执行参数化的 SQL 语句,能够将指标直接写入与 SQL 兼容的数据库(如 MariaDB)。通过支持 MySQL 驱动程序,该插件与 MariaDB 无缝集成,实现可靠、结构化的指标存储。此设置非常适合喜欢基于 SQL 的分析或希望将指标与业务数据一起存储以进行统一查询的用户。MariaDB 是 MySQL 的一个社区开发的、企业级的分支,强调性能、安全性以及开放性。该插件支持将时序指标插入到自定义模式中,从而可以使用 SQL 连接器灵活地进行分析,并与 Metabase 或 Grafana 等 BI 工具集成。
配置
Suricata
[[inputs.suricata]]
## Source
## Data sink for Suricata stats log. This is expected to be a filename of a
## unix socket to be created for listening.
# source = "/var/run/suricata-stats.sock"
## Delimiter
## Used for flattening field keys, e.g. subitem "alert" of "detect" becomes
## "detect_alert" when delimiter is "_".
# delimiter = "_"
## Metric version
## Version 1 only collects stats and optionally will look for alerts if
## the configuration setting alerts is set to true.
## Version 2 parses any event type message by default and produced metrics
## under a single metric name using a tag to differentiate between event
## types. The timestamp for the message is applied to the generated metric.
## Additional tags and fields are included as well.
# version = "1"
## Alerts
## In metric version 1, only status is captured by default, alerts must be
## turned on with this configuration option. This option does not apply for
## metric version 2.
# alerts = false
MariaDB
[[outputs.sql]]
## Database driver
## Valid options: mssql (Microsoft SQL Server), mysql (MySQL), pgx (Postgres),
## sqlite (SQLite3), snowflake (snowflake.com) clickhouse (ClickHouse)
driver = "mysql"
## Data source name
## The format of the data source name is different for each database driver.
## See the plugin readme for details.
data_source_name = "username:password@tcp(host:port)/dbname"
## Timestamp column name
timestamp_column = "timestamp"
## Table creation template
## Available template variables:
## {TABLE} - table name as a quoted identifier
## {TABLELITERAL} - table name as a quoted string literal
## {COLUMNS} - column definitions (list of quoted identifiers and types)
table_template = "CREATE TABLE {TABLE}({COLUMNS})"
## SQL INSERT statement with placeholders. Telegraf will substitute values at runtime.
## table_template = "INSERT INTO metrics (timestamp, name, value, tags) VALUES (?, ?, ?, ?)"
## Table existence check template
## Available template variables:
## {TABLE} - tablename as a quoted identifier
table_exists_template = "SELECT 1 FROM {TABLE} LIMIT 1"
## Initialization SQL
init_sql = "SET sql_mode='ANSI_QUOTES';"
## Maximum amount of time a connection may be idle. "0s" means connections are
## never closed due to idle time.
connection_max_idle_time = "0s"
## Maximum amount of time a connection may be reused. "0s" means connections
## are never closed due to age.
connection_max_lifetime = "0s"
## Maximum number of connections in the idle connection pool. 0 means unlimited.
connection_max_idle = 2
## Maximum number of open connections to the database. 0 means unlimited.
connection_max_open = 0
## NOTE: Due to the way TOML is parsed, tables must be at the END of the
## plugin definition, otherwise additional config options are read as part of the
## table
## Metric type to SQL type conversion
## The values on the left are the data types Telegraf has and the values on
## the right are the data types Telegraf will use when sending to a database.
##
## The database values used must be data types the destination database
## understands. It is up to the user to ensure that the selected data type is
## available in the database they are using. Refer to your database
## documentation for what data types are available and supported.
#[outputs.sql.convert]
# integer = "INT"
# real = "DOUBLE"
# text = "TEXT"
# timestamp = "TIMESTAMP"
# defaultvalue = "TEXT"
# unsigned = "UNSIGNED"
# bool = "BOOL"
# ## This setting controls the behavior of the unsigned value. By default the
# ## setting will take the integer value and append the unsigned value to it. The other
# ## option is "literal", which will use the actual value the user provides to
# ## the unsigned option. This is useful for a database like ClickHouse where
# ## the unsigned value should use a value like "uint64".
# # conversion_style = "unsigned_suffix"
输入和输出集成示例
Suricata
-
网络流量分析:利用 Suricata 插件跟踪有关网络入侵尝试和性能的详细指标,帮助实时威胁检测和响应。通过可视化捕获的警报和流量统计信息,安全团队可以快速查明漏洞并降低风险。
-
性能监控仪表板:使用 Suricata Telegraf 插件指标创建一个仪表板,以监控 IDS/IPS 引擎的健康状况和性能。此用例提供了内存使用率、捕获的数据包和警报统计信息的概览,使团队能够保持最佳运行状态。
-
自动化安全报告:利用该插件生成关于警报统计信息和流量模式的定期报告,帮助安全分析师识别长期趋势并制定战略防御计划。自动化报告还确保持续评估网络的安全性。
-
实时警报处理:将 Suricata 的警报指标集成到更广泛的事件响应自动化框架中。通过整合来自 Suricata 插件的输入,组织可以开发智能触发器,用于警报和自动化响应工作流程,从而提高对潜在威胁的反应速度。
MariaDB
-
商业智能集成:将应用程序性能指标直接存储到 MariaDB 中,并将其连接到 Metabase 或 Apache Superset 等 BI 工具。此设置允许将运营数据与业务 KPI 融合到统一的仪表板中,从而提高跨部门的可见性。
-
具有历史指标的合规性报告:使用此插件将指标记录到 MariaDB 中,用于审计和合规性用例。关系模型可以精确查询带有时间戳条目的过去性能指标,从而支持法规文档。
-
基于 SQL 逻辑的自定义警报:将指标插入 MariaDB,并使用自定义 SQL 查询来定义警报阈值或条件。与 cron 作业或计划脚本结合使用,这可以实现传统指标平台无法实现的高级警报工作流程。
-
物联网传感器指标存储:通过 Telegraf 从物联网设备收集传感器数据,并使用规范化模式将其存储在 MariaDB 中。这种方法具有成本效益,并且与现有的基于 SQL 的系统集成良好,可用于实时或历史分析。
反馈
感谢您成为我们社区的一份子!如果您有任何一般性反馈或在这些页面上发现了任何错误,我们欢迎并鼓励您提供意见。请在 InfluxDB 社区 Slack 中提交您的反馈。