Suricata and Google BigQuery Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider Suricata and InfluxDB.

5B+

Telegraf downloads

#1

Time series database
Source: DB Engines

1B+

Downloads of InfluxDB

2,800+

Contributors

Table of Contents

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Input and output integration overview

This plugin reports internal performance counters of the Suricata IDS/IPS engine and processes the incoming data to fit Telegraf’s format.

The Google BigQuery plugin allows Telegraf to write metrics to Google Cloud BigQuery, enabling robust data analytics capabilities for telemetry data.

Integration details

Suricata

The Suricata plugin captures and reports internal performance metrics from the Suricata IDS/IPS engine, which includes a wide range of statistics such as traffic volume, memory usage, uptime, and counters for flows and alerts. This plugin listens for JSON-formatted log outputs from Suricata, allowing it to parse and format the data for integration with Telegraf. It operates as a service input plugin, meaning it actively waits for metrics or events from Suricata rather than collecting metrics at predefined intervals. The plugin supports configurations for different metrics versions allowing for enhanced flexibility and detailed data gathering.

Google BigQuery

The Google BigQuery plugin for Telegraf enables seamless integration with Google Cloud’s BigQuery service, a popular data warehousing and analytics platform. This plugin facilitates the transfer of metrics collected by Telegraf into BigQuery datasets, making it easier for users to perform analyses and generate insights from their telemetry data. It requires authentication through a service account or user credentials and is designed to handle various data types, ensuring that users can maintain the integrity and accuracy of their metrics as they are stored in BigQuery tables. The configuration options allow for customization around dataset specifications and handling metrics, including the management of hyphens in metric names, which are not supported by BigQuery for streaming inserts. This plugin is particularly useful for organizations leveraging the scalability and powerful query capabilities of BigQuery to analyze large volumes of monitoring data.

Configuration

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

Google BigQuery

# Configuration for Google Cloud BigQuery to send entries
[[outputs.bigquery]]
  ## Credentials File
  credentials_file = "/path/to/service/account/key.json"

  ## Google Cloud Platform Project
  # project = ""

  ## The namespace for the metric descriptor
  dataset = "telegraf"

  ## Timeout for BigQuery operations.
  # timeout = "5s"

  ## Character to replace hyphens on Metric name
  # replace_hyphen_to = "_"

  ## Write all metrics in a single compact table
  # compact_table = ""
  

Input and output integration examples

Suricata

  1. Network Traffic Analysis: Utilize the Suricata plugin to track detailed metrics about network intrusion attempts and performance, aiding in real-time threat detection and response. By visualizing captured alerts and flow statistics, security teams can quickly pinpoint vulnerabilities and mitigate risks.

  2. Performance Monitoring Dashboard: Create a dashboard using the Suricata Telegraf plugin metrics to monitor the health and performance of the IDS/IPS engine. This use case provides an overview of memory usage, captured packets, and alert statistics, allowing teams to maintain optimal operating conditions.

  3. Automated Security Reporting: Leverage the plugin to generate regular reports on alert statistics and traffic patterns, helping security analysts to identify long-term trends and prepare strategic defense initiatives. Automated reports also ensure that the security posture of the network is continually assessed.

  4. Real-time Alert Handling: Integrate Suricata’s alert metrics within a broader incident response automation framework. By incorporating the inputs from the Suricata plugin, organizations can develop smart triggers for alerting and automated response workflows that enhance reaction times to potential threats.

Google BigQuery

  1. Real-Time Analytics Dashboard: Leverage the Google BigQuery plugin to feed live metrics into a custom analytics dashboard hosted on Google Cloud. This setup would allow teams to visualize performance data in real-time, providing insights into system health and usage patterns. By using BigQuery’s querying capabilities, users can easily create tailored reports and dashboards to meet their specific needs, thus enhancing decision-making processes.

  2. Cost Management and Optimization Analysis: Utilize the plugin to automatically send cost-related metrics from various services into BigQuery. Analyzing this data can help businesses identify unnecessary expenses and optimize resource usage. By performing aggregation and transformation queries in BigQuery, organizations can create accurate forecasts and manage their cloud spending efficiently.

  3. Cross-Team Collaboration on Monitoring Data: Enable different teams within an organization to share their monitoring data using BigQuery. With the help of this Telegraf plugin, teams can push their metrics to a central BigQuery instance, fostering collaboration. This data-sharing approach encourages best practices and cross-functional awareness, leading to collective improvements in system performance and reliability.

  4. Historical Analysis for Capacity Planning: By using the BigQuery plugin, companies can collect and store historical metrics data essential for capacity planning. Analyzing trends over time can help anticipate system needs and scale infrastructure proactively. Organizations can create time-series analyses and identify patterns that inform their long-term strategic decisions.

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Related Integrations

HTTP and InfluxDB Integration

The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.

View Integration

Kafka and InfluxDB Integration

This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.

View Integration

Kinesis and InfluxDB Integration

The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.

View Integration