Logging use cases for clusters, collectors, syslog, and incident response

Use this page when Fluent Bit tails container logs, adds host or container context, and forwards the result into Fluxtail for reading.

Use this path when rsyslog, syslog-ng, appliances, VMs, or network devices already emit syslog and need one readable destination.

Use this path when syslog-ng is already your routing layer and you want the destination side to handle reading, filtering, alerts, and AI diagnostics.

Use this path when container stdout, JSON logs, or collector-forwarded Docker logs need one central place for live reading.

Use this path when application logs already carry service names, trace IDs, span IDs, deployment context, or other telemetry fields.

Use this path when the main job is reading recent logs, narrowing the time window, and keeping noisy streams understandable while traffic is still arriving.

Use this path when MCP tools or built-in AI chat should inspect recent errors, exception clusters, receiver health, or no-log cases from the same Fluxtail account.

Use this path when several sources need to land in named streams with shared search, filters, retention, and team access.