Log Sources

Depending on the origins of the logs, it may be necessary to adopt a different approach for the installation and configuration of FluentBit.

However, to provide convenient parsing and data labeling, we accept 4 different log sources, which need a different setup and configuration.

Kubernetes

You may need this method to collect and ship your Kubernetes application's logs. FluentBit offers a wide range of information on how to set up FluentBit on your Kubernetes cluster. However, you are welcome to try our Example Kubernetes Configuration.

Docker

If you have a set of applications on Docker, we recommend using our Example Docker configuration. However, you can find more information about Docker configuration on FluentBit's official website.

Linux Systemd

To set up FluentBit in a Linux system with systems, journald you need to install an appropriate package for your distribution. Instructions on doing so can be found on the FluentBit's official website. You can find a sample configuration in our Example Section.

HTTP (JSON)

You can even send logs in a JSON format through our HTTP REST endpoint. Example:

curl -X "POST" "https://12be6dbe134f-logs.3b0b424eb27f.logging.de-txl.ionos.com/myhttp" \
     -H 'Content-Type: application/json' \
     -H 'APIKEY: <KEY>' \
     -d $'{
  "status": "Ready",
  "ts": 1580306777.04728,
  "pod": {
    "name": "Example Name",
    "namespace": "data"
  },
  "msg": "Pod status updated",
  "level": "error",
  "label_1": "test label"
}'

Note: Technically, you can send logs with FluentBit from any sources as long as the communication is supported: TCP and HTTP(JSON). However, at the moment, we provide convenient parsing with the above log sources.

Last updated

Revision created

Minor update from the comments