Configure Fluent Bit to collect, parse, and forward log data from several different sources to Datadog for monitoring. Fluent Bit has a small memory footprint (~450 KB), so you can use it to collect logs in environments with limited resources, such as containerized services and embedded Linux systems. Datadog’s Fluent Bit output plugin supports Fluent Bit v1.3.0+.
Find below instructions to configure Fluent Bit on a host, if you want to configure it on AWS ECS, see the ECS Fluent Bit and FireLens documentation.
[OUTPUT]configuration section, see the Configuration file example.
|Host||Required - The Datadog server where you are sending your logs.|
|TLS||Required - End-to-end security communications security protocol. Datadog recommends setting this to |
|apikey||Required - Your Datadog API key.|
|compress||Recommended - compresses the payload in GZIP format, Datadog supports and recommends setting this to |
|dd_service||Recommended - The human readable name for your service generating the logs - the name of your application or database.|
|dd_source||Recommended - A human readable name for the underlying technology of your service. For example, |
|dd_message_key||Recommended - Set the attribute to use to store your log message.|
|dd_tags||Optional - The tags you want to assign to your logs in Datadog.|
|provider||Optional - The provider to use. Set this to |
[OUTPUT] Name datadog Match * Host http-intake.logs.datadoghq.com TLS on compress gzip apikey <DATADOG_API_KEY> dd_service <APPLICATION_SERVICE> dd_source <SOURCE> dd_message_key log dd_tags env:dev,<TAG_KEY>:<TAG_VALUE>
Need help? Contact Datadog support.
Additional helpful documentation, links, and articles: