> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/audit/logs/scenarios/export-to-filebeat.md).

# Send Local Logs to Filebeat

**Scenario:** You want to save gateway/relay logs to Filebeat. This guide presents a simple method to automatically send all gateway/relay logs to Filebeat, which is a common ingestion tool for solutions like ElasticSearch.

{% hint style="info" %}
As with all gateway/relay logs, the logs stored on the gateway/relay will not include Admin UI activities, which can be accessed via the `sdm audit activities` command.
{% endhint %}

### Setting up the export

1. Enable relay logging in the Admin UI under *Settings / Log Encryption & Storage*. Ensure logging is set to FILE.
2. Use [these instructions](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation-configuration.html) to install the Filebeat client on each gateway or relay.
3. Create a [manual input configuration](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-options.html) that looks like the following:

   ```yml
   paths:
       - /home/sdm/.sdm/logs/*.log
   include_lines: ['uuid\":\"0']
   ```
4. Modify the second line to use the absolute path to the SDM logs on your machine.
5. The `include_lines` entry parses the log format to include the uuid (the unique id for each log event) and events of type "0", which are database queries.
6. You can omit the `include_lines` entry if you would like to capture all events.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.strongdm.com/admin/audit/logs/scenarios/export-to-filebeat.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.