> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/integrations/list-of-integrations/fluent-bit/fluent-bit-head-plugin.md).

# Fluent-bit Head Plugin

### How to Integrate Fluent-bit Head Plugin with Apica Ascent

#### 1. Introduction

This guide explains how to send Head metrics to Apica Ascent with Fluent-bit, and how to view them.

#### 2. Configure the Head Plugin in Fluent-bit

Update your Fluent-bit.conf with an input and filter for the Head Plugin:

```
[INPUT]
    Name    head
    Tag     head
    File    /var/log/prometheus/prometheus.log.1
```

```
[FILTER]
    Name   modify
    Match  head
    Add    namespace Fluent-bit
    Add    app_name Head
```

Restart Fluent-bit with `systemctl restart fluent-bit` and check the status with `systemctl status fluent-bit` to verify that it’s running correctly.

Helpful links:

* [Official Plugin documentation.](https://docs.fluentbit.io/manual/pipeline/inputs/forward)
* [Set up Fluent-bit for Apica Ascent.](https://docs.apica.io/integrations/list-of-integrations/fluent-bit#fluent-bit-configuration)

#### 3. Verify Logs in Apica Ascent

1\.     Log in to Apica Ascent

2\.     Navigate to Explore → Logs & Insights

3\.     Look for the namespace and application name specified in the config file\
Example:

<figure><img src="/files/8bsjiiSlKL4LUXgevsNu" alt=""><figcaption></figcaption></figure>

#### 4.Example logs

Message:

{% code overflow="wrap" %}

```
{"app_name":"Head","date":1765563662.187878,"head":"time=2025-12-08T01:00:06.395Z level=INFO source=compact.go:598 msg=\"write block\" component=tsdb mint=1765144800590 maxt=1765152000000 ulid=01KBXQHYFTT25P541BJP6TABK2 duration=5.504793919s ooo=false\ntime=2025-12-08T01:00:06.597Z level=INFO source=db.go:1824","namespace":"Fluent-bit"}
```

{% endcode %}

StructuredData :

```
_size: 338
date: 1765563662.187878
head: time=2025-12-08T01:00:06.395Z level=INFO source=compact.go:598 msg="write block" component=tsdb mint=1765144800590 maxt=1765152000000 ulid=01KBXQHYFTT25P541BJP6TABK2 duration=5.504793919s ooo=false
time=2025-12-08T01:00:06.597Z level=INFO source=db.go:1824
```

#### 5. Troubleshooting

&#x20; [**Fluent-bit Troubleshooting**](https://docs.apica.io/integrations/list-of-integrations/fluent-bit/fluent-bit-troubleshooting)


---

# 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.apica.io/integrations/list-of-integrations/fluent-bit/fluent-bit-head-plugin.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.