> 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-exec-plugin.md).

# Fluent-bit Exec Plugin

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

#### 1. Introduction

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

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

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

```
[INPUT]
    Name     exec
    Tag      exec
    Command  ls /var/log
```

```
[FILTER]
    Name          modify
    Match         exec
    Add namespace Fluent-bit
    Add app_name  Exec
```

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/data-pipeline/inputs/exec)
* [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/Me2rYc8dgQovPwuxR1YR" alt=""><figcaption></figcaption></figure>

#### 4. Example logs

Message:

{% code overflow="wrap" %}

```
{"app_name":"Exec","date":1765529639.190001,"exec":"syslog","namespace":"Fluent-bit"}
```

{% endcode %}

StructuredData :

```
_size: 85
date: 1765529639.190001
exec: syslog
```

#### 5. Troubleshooting

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