> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/developer-guide/development-cycle/dashboards/completed-executions/pipeline-execution-logs-download.md).
# Pipeline execution logs download
{% hint style="info" %}
**Important information:**
* To access Pipeline Execution Logs Download and use all the features in this article, you need to have permission EXPORT:READ. Learn more in the[ Roles documentation](/documentation/developer-guide/platform-administration/administration/new-access-control/access-control-roles.md).
* The default Support, Developers, and Governance Manager groups already have permissions, but if you prefer, you can add the system role to your access group.
{% endhint %}
You can download logs of a given pipeline execution related to a specific pipeline execution key in CSV format via the page **Executions** in Monitor.
A **pipeline execution key** is a unique identifier for each execution of a pipeline.
To use the feature, follow the steps below:
1. Access the **Executions** page.
2. On the box icon, under the Action column, click **Download Execution Logs**.
3. On the confirmation dialog (pop-up), click **Download pipeline execution key logs**, then **Download** and obtain a CSV file up to 5MB.
The CSV file contains the following information:
* timestamp
* realm
* pipelineKey
* pipelineName
* logLevel
* logMessage
It’s now also possible to customize the separator by characters of the user’s choice, limited to one character at a time, being the default character a “;” (semicolon). Note that you must select the same exported character separator when opening the file in the CSV reader for it to work correctly.
---
# 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.digibee.com/documentation/developer-guide/development-cycle/dashboards/completed-executions/pipeline-execution-logs-download.md?ask=&goal=
```
`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.