> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/misc/logs.md).

# Logs

Know what happened and who did it

Everywhere on the platform you can find links to logs. These are tiny pieces of text that show you what changed and who changed it. This is a very useful feature to answer questions like:

* Did this member receive a ticket via email?
* Who checked out this guest?
* When did this person confirm their shiftpicker choice?
* Has it always been this name for that stock item?
* Which [zone scanner](https://docs.eventication.com/event/misc/4g-scan-devices.md) checked this person into this zone?
* Who printed the [wristband](https://docs.eventication.com/event/misc/wristbands.md) for this visitor?
* When was the last time their wristband was scanned, and where?
* Who added this day to this guest?

<figure><img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fgit-blob-ef5ed4787933d8df6ea9d3c35005215def917cbf%2FScreenshot%202023-09-01%20at%2021.29.44.jpg?alt=media" alt="" width="375"><figcaption><p>An example of a log</p></figcaption></figure>

Every page that shows these logs now has a "*Download*" button. The platform will create and fill a CSV file and email it to you when it's ready.

{% hint style="info" %}
Currently there is a limit of 10.000 logs that can be downloaded.
{% endhint %}


---

# 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.eventication.com/event/misc/logs.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.
