What problem does it solve?
Distributed infrastructure generates logs across many endpoints, and without a unified forwarding pipeline, security teams lose visibility, drop events under load, and cannot feed SIEM platforms reliably. This Skill guides the deployment of Fluent Bit forwarders and a central Fluentd aggregator so logs are collected, filtered, enriched, and delivered to Elasticsearch, S3, or Splunk.
Core Features & Use Cases
- Endpoint and aggregator configuration: Generate Fluent Bit input/filter/output configs and Fluentd forward-input, parsing, and multi-output routing configurations.
- Filtering and enrichment: Apply record_transformer and grep filters to enrich events and reduce noise before delivery.
- Validation and testing: Validate configuration syntax with dry runs and confirm end-to-end delivery using fluent-logger test events.
- Use Case: A security operations team needs syslog and application logs from dozens of servers forwarded over TLS-authenticated channels into Elasticsearch and Splunk, with file-based buffering so no events are lost during bursts or restarts.
Quick Start
Generate a Fluent Bit and Fluentd configuration that forwards syslog and application logs over TLS to Elasticsearch with file-based buffering and delivery verification.