fluentbit-generator

Generate Fluent Bit configurations for Kubernetes log pipelines with inputs, filters, and outputs.

290|32|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/akin-ozer/cc-devops-skills --skill fluentbit-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fluentbit-generator
Source: https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/fluentbit-generator
Command: npx skills add https://github.com/akin-ozer/cc-devops-skills --skill fluentbit-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the generation of production-ready Fluent Bit configurations, enabling teams to quickly set up robust log pipelines with best practices.

Core Features & Use Cases

  • Generate complete Fluent Bit configurations or individual sections (SERVICE, INPUT, FILTER, OUTPUT, PARSER) with sensible defaults.
  • Create Kubernetes-ready log pipelines to collect pod logs and forward to destinations such as Elasticsearch, Grafana Loki, S3, Kafka.
  • Validate and adapt configurations for performance and reliability, including memory limits, TLS, retry policies, and Parsers_File references.

Quick Start

Use this skill to generate a Kubernetes-to-Elasticsearch Fluent Bit config, then customize the hosts and paths as needed.

Frequently Asked Questions about fluentbit-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Fluent Bit config for Kubernetes log pipelines?

Generate a Fluent Bit config for Kubernetes log pipelines by automating inputs, filters, and outputs with sensible defaults for pod logs. The configuration supports destinations like Elasticsearch, Loki, S3, and Kafka with metadata enrichment.

What is the best way to configure Fluent Bit multiline parsing and Parsers_File references?

Configure Fluent Bit multiline parsing and Parsers_File references by generating a dedicated parsers configuration workflow. This approach applies production-ready best practices for parsing complex log streams and validating external parser file usage.

Can I generate individual Fluent Bit sections like SERVICE, INPUT, FILTER, OUTPUT, and PARSER?

Yes, you can generate individual Fluent Bit sections like SERVICE, INPUT, FILTER, OUTPUT, and PARSER. The generator creates complete configurations or isolated sections with sensible defaults tailored to your specific log pipeline requirements.

Does the generated Fluent Bit configuration include TLS, retry policies, and per-input memory limits?

Yes, the generated Fluent Bit configuration includes TLS, retry policies, and per-input memory limits. It validates and adapts configurations specifically for performance and reliability in production-ready containerized environments.

Why does my Fluent Bit Kubernetes config need metadata enrichment for pod logs?

Fluent Bit Kubernetes configs need metadata enrichment for pod logs to properly contextualize container outputs. Generating Kubernetes-ready pipelines automatically applies this enrichment before forwarding logs to destinations like Elasticsearch or Grafana Loki.