> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/~/revisions/1AlFSZBNMIBgs7fiOwFD/early-access/logging-service/user-how-tos/send-logs-to-platform.md).

# Send Logs to Platform

In order to send logs to the logging platform, there are a few requirements you need to have:

1. A `Ready` pipeline instance so that you can obtain `tcpAddress` or `httpAddress`.
2. A [key](/cloud/~/revisions/1AlFSZBNMIBgs7fiOwFD/early-access/logging-service/api-how-tos/obtain-key.md) that you already obtained.
3. FluentBit log agent installed in your platform ([see more](broken://pages/JzAryZIl7h0ECdUTjxFl)).

Based on your infrastructure, whether it is `kubernetes`, `docker`, or `systemd`, you may follow different instructions to set up and install FluentBit. However, there are a few pieces of information that you always need to configure FluentBit's output section:

* The **log server endpoint**, which is `tcpAddress` or `httpAddress` based on your log source.
* The **Key** that is needed for the authentication.
* The **Tag** that you defined while creating the pipeline.

Here is an example of a FluentBit configuration that needs an Endpoint, Tag, and Key:

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

{% hint style="warning" %}
**Note:** The port is always **9000** if the protocol is TCP.
{% endhint %}

### Troubleshooting

FluentBit can be configured to expose more verbose logs for troubleshooting purposes.

```editorconfig
[OUTPUT]
    Log_Level      debug
```

For more information, see [FluentBit global configuration](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/classic-mode/configuration-file).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/~/revisions/1AlFSZBNMIBgs7fiOwFD/early-access/logging-service/user-how-tos/send-logs-to-platform.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.