iptables and Sumo Logic Integration

Input and output integration overview

The iptables plugin for Telegraf collects metrics on packet and byte counts for specified iptables rules, providing insights into firewall activity and performance.

The Sumo Logic plugin is designed to facilitate the sending of metrics from Telegraf to Sumo Logic’s HTTP Source. By utilizing this plugin, users can analyze their metric data in the Sumo Logic platform, leveraging various output data formats.

Integration details

iptables

The iptables plugin gathers packets and bytes counters for rules within a set of table and chain from the Linux iptables firewall. The plugin monitors rules identified by associated comments, as rules without comments are ignored. This approach ensures a unique identification for the monitored rules, which is particularly important since the rule number can change dynamically as rules are modified. To use this plugin effectively, users must name their rules with unique comments. The plugin also requires elevated permissions (CAP_NET_ADMIN and CAP_NET_RAW) to run, which can be configured either by running Telegraf as root (discouraged), using systemd capabilities, or by configuring sudo appropriately. Additionally, defining multiple instances of the plugin might lead to conflicts; thus, using locking mechanisms in the configuration is recommended to avoid errors during concurrent accesses.

Sumo Logic

This plugin facilitates the transmission of metrics to Sumo Logic’s HTTP Source, employing specified data formats for HTTP messages. Telegraf, which must be version 1.16.0 or higher, can send metrics encoded in several formats, including graphite, carbon2, and prometheus. These formats correspond to different content types recognized by Sumo Logic, ensuring that the metrics are correctly interpreted for analysis. Integration with Sumo Logic allows users to leverage a comprehensive analytics platform, enabling rich visualizations and insights from their metric data. The plugin provides configuration options such as setting URLs for the HTTP Metrics Source, choosing the data format, and specifying additional parameters like timeout and request size, which enhance flexibility and control in data monitoring workflows.

Configuration

iptables

[[inputs.iptables]]
  ## iptables require root access on most systems.
  ## Setting 'use_sudo' to true will make use of sudo to run iptables.
  ## Users must configure sudo to allow telegraf user to run iptables with
  ## no password.
  ## iptables can be restricted to only list command "iptables -nvL".
  use_sudo = false
  ## Setting 'use_lock' to true runs iptables with the "-w" option.
  ## Adjust your sudo settings appropriately if using this option
  ## ("iptables -w 5 -nvl")
  use_lock = false
  ## Define an alternate executable, such as "ip6tables". Default is "iptables".
  # binary = "ip6tables"
  ## defines the table to monitor:
  table = "filter"
  ## defines the chains to monitor.
  ## NOTE: iptables rules without a comment will not be monitored.
  ## Read the plugin documentation for more information.
  chains = [ "INPUT" ]

Sumo Logic

[[outputs.sumologic]]
  ## Unique URL generated for your HTTP Metrics Source.
  ## This is the address to send metrics to.
  # url = "https://events.sumologic.net/receiver/v1/http/"

  ## Data format to be used for sending metrics.
  ## This will set the "Content-Type" header accordingly.
  ## Currently supported formats:
  ## * graphite - for Content-Type of application/vnd.sumologic.graphite
  ## * carbon2 - for Content-Type of application/vnd.sumologic.carbon2
  ## * prometheus - for Content-Type of application/vnd.sumologic.prometheus
  ##
  ## More information can be found at:
  ## https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/HTTP-Source/Upload-Metrics-to-an-HTTP-Source#content-type-headers-for-metrics
  ##
  ## NOTE:
  ## When unset, telegraf will by default use the influx serializer which is currently unsupported
  ## in HTTP Source.
  data_format = "carbon2"

  ## Timeout used for HTTP request
  # timeout = "5s"

  ## Max HTTP request body size in bytes before compression (if applied).
  ## By default 1MB is recommended.
  ## NOTE:
  ## Bear in mind that in some serializer a metric even though serialized to multiple
  ## lines cannot be split any further so setting this very low might not work
  ## as expected.
  # max_request_body_size = 1000000

  ## Additional, Sumo specific options.
  ## Full list can be found here:
  ## https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/HTTP-Source/Upload-Metrics-to-an-HTTP-Source#supported-http-headers

  ## Desired source name.
  ## Useful if you want to override the source name configured for the source.
  # source_name = ""

  ## Desired host name.
  ## Useful if you want to override the source host configured for the source.
  # source_host = ""

  ## Desired source category.
  ## Useful if you want to override the source category configured for the source.
  # source_category = ""

  ## Comma-separated key=value list of dimensions to apply to every metric.
  ## Custom dimensions will allow you to query your metrics at a more granular level.
  # dimensions = ""
</code></pre>

Input and output integration examples

iptables

1. Monitoring Firewall Performance: Monitor the performance and efficiency of your firewall rules in real time. By tracking packet and byte counters, network administrators can identify which rules are most active and may require optimization. This enables proactive management of firewall configurations to enhance security and performance, especially in environments where dynamic adjustments are frequently made.

2. Understanding Traffic Patterns: Analyze incoming and outgoing traffic patterns based on specific rules. By leveraging the metrics gathered by this plugin, system admins can gain insights into which services are receiving the most traffic, effectively identifying popular services and potential security threats from unusual traffic spikes.

3. Automated Alerting on Traffic Anomalies: Integrate the iptables plugin with an alerting system to notify administrators of unusual activity detected by the firewall. By setting thresholds on the collected metrics, such as sudden increases in packets dropped or unexpected protocol use, teams can automate responses to potential security incidents, enabling swift remediation of threats to the network.

4. Comparative Analysis of Firewall Rules: Conduct comparative analyses of different firewall rules over time. By collecting historical packet and byte metrics, organizations can evaluate the effectiveness of various rules, making data-driven decisions on which rules to modify, reinforce, or remove altogether, thus streamlining their firewall configurations.

Sumo Logic

1. Real-Time System Monitoring Dashboard: Utilize the Sumo Logic plugin to continuously feed performance metrics from your servers into a Sumo Logic dashboard. This setup allows tech teams to visualize system health and load in real-time, enabling quicker identification of any performance bottlenecks or system failures through detailed graphs and metrics.

2. Automated Alerting System: Configure the plugin to send metrics that trigger alerts in Sumo Logic for specific thresholds such as CPU usage or memory consumption. By setting up automated alerts, teams can proactively address issues before they escalate into critical failures, significantly improving response times and overall system reliability.

3. Cross-System Metrics Aggregation: Integrate multiple Telegraf instances across different environments (development, testing, production) and funnel all metrics to a central Sumo Logic instance using this plugin. This aggregation enables comprehensive analysis across environments, facilitating better monitoring and informed decision-making across the software development lifecycle.

4. Custom Metrics with Dimensions Tracking: Use the Sumo Logic plugin to send customized metrics that include dimensions identifying various aspects of your infrastructure (e.g., environment, service type). This granular tracking allows for more tailored analytics, enabling your team to dissect performance across different application layers or business functions.

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.