Send Logs to the Platform

You can send logs to the Logging Service using Fluent Bit, or natively in the OpenTelemetry Protocol (OTLP) format. Based on your infrastructure—Kubernetes, Docker, Linux Systemd, HTTP, or OTLP—the configuration differs.

Prerequisites:

• A Ready pipeline instance. To obtain tcpAddress or httpAddress, see Set Up a Logging Pipeline.
• A key obtained from the REST API.
• Fluent Bit installed on your system. For more information, refer to the Getting Started with Fluent Bit Documentation.

1

Obtain the pipeline endpoint

After creating a pipeline, the response includes either a tcpAddress or httpAddress. Save this value.

Example TCP endpoint:

12be6dbe134f-logs.3b0b424eb27f.logging.de-txl.ionos.com

Example HTTP endpoint:

https://12be6dbe134f-logs.3b0b424eb27f.logging.de-txl.ionos.com

2

Obtain a key

Use the Shared_Key (TCP) or APIKEY (HTTP) returned when you created the pipeline for authentication. To generate a new key, see Obtain a new Key.

Configure Fluent Bit

Each log source requires the pipeline endpoint and a key.

Kubernetes

1. Install the Fluent Bit package for your Kubernetes distribution. For more information, refer to the Fluent Bit on Kubernetes Documentation.
2. Update the Fluent Bit configuration with the tcpAddress and Shared_Key.
3. Run Fluent Bit to forward logs to the Logging Service.

[OUTPUT]
    Name            forward
    Match           *
    Port            9000
    Tag             <TAG>
    Host            <TCP_ENDPOINT>
    tls             on
    Shared_Key      <KEY>

Warning: The port must be set to 9000 when using TCP.

Note: For more information, refer to the Kubernetes configuration examples.

Docker

1. Install the Fluent Bit package for Docker. For more information, refer to the Fluent Bit on Docker Documentation.
2. Update the Fluent Bit configuration with the tcpAddress and Shared_Key.
3. Run Fluent Bit to forward logs to the Logging Service.

[OUTPUT]
    Name            forward
    Match           *
    Port            9000
    Tag             <TAG>
    Host            <TCP_ENDPOINT>
    tls             on
    Shared_Key      <KEY>

Warning: The port must be set to 9000 when using TCP.

Note: For more information, refer to the Docker configuration examples.

Linux Systemd

1. Install the appropriate Fluent Bit package for your Linux distribution. For more information, refer to the Getting Started with Fluent Bit Documentation.
2. Update the Fluent Bit configuration with the tcpAddress and Shared_Key.
3. Run Fluent Bit to forward logs to the Logging Service.

[OUTPUT]
    Name            forward
    Match           *
    Port            9000
    Tag             <TAG>
    Host            <TCP_ENDPOINT>
    tls             on
    Shared_Key      <KEY>

Warning: The port must be set to 9000 when using TCP.

Note: For more information, refer to the Linux Systemd configuration examples.

HTTP

Send logs directly via the HTTP REST endpoint. Only JSON-formatted logs are supported.

curl --location \
--request POST 'https://<HTTP_ENDPOINT>/<TAG>' \
--header 'Content-Type: application/json' \
--header 'APIKEY: <KEY>' \
--data '{
    "status": "Ready",
    "ts": 1580306777.04728,
    "pod": {
        "name": "Example Name",
        "namespace": "data"
    },
    "msg": "Pod status updated",
    "level": "error",
    "label_1": "test label"
}'

Alternatively, configure Fluent Bit to use the HTTP output plugin:

[OUTPUT]
    Name            http
    Match           *
    Host            <HTTPS_ENDPOINT>
    URI             /<TAG>
    Format          json
    Header          APIKEY <KEY>
    tls             on
    Port            443

OTLP

Send logs directly in the OpenTelemetry Protocol (OTLP) format. This does not require Fluent Bit and works with any OTLP-compliant client, including the OpenTelemetry Collector.

curl --location \
--request POST 'https://<HTTP_ENDPOINT>/<TAG>' \
--header 'Content-Type: application/json' \
--header 'APIKEY: <KEY>' \
--data '{
  "resourceLogs": [
    {
      "resource": {
        "attributes": [
          { "key": "service.name", "value": { "stringValue": "my-payment-service" } }
        ]
      },
      "scopeLogs": [
        {
          "scope": { "name": "manual-http-logger" },
          "logRecords": [
            {
              "timeUnixNano": "1780669755483587000",
              "severityText": "INFO",
              "severityNumber": 9,
              "body": { "stringValue": "Transaction processed successfully for user_id 9482." }
            }
          ]
        }
      ]
    }
  ]
}'

Alternatively, configure an OpenTelemetry Collector otlphttp exporter:

exporters:
  otlphttp:
    logs_endpoint: "https://<HTTP_ENDPOINT>/<TAG>"
    headers:
      APIKEY: "<KEY>"

Troubleshooting

1. Verify: Open the Logging Service dashboard and confirm that logs appear.
2. Invalid key: Check that you copied the correct Shared_Key or APIKEY.
3. Connection errors: Verify outbound access on port 9000 (TCP) or port 443 (HTTP).
4. No logs displayed: Enable verbose logging in Fluent Bit:

[OUTPUT]
    Log_Level      debug

For more information, see Fluent Bit global configuration.