> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/streamlog/streamlog-user-documentation/quick-start-guide/streamlog-operation/editors-tabs/events-tab.md).

# Events Tab

The ‘Events’ Tab lists all the ‘Triggers’ in the ‘Configuration’ within the ‘Project’, along with information such as the number of events and the first and last occurrence.

The panel also displays the actual events and their recorded location (if available).

Triggers set within the ‘Configuration’ found in the selected ‘Project’ describe each trigger and the number of events that occurred for each, with their first and last occurrences.

Events position provides a graphical plotting of the vehicle location for each event for the selected trigger.

{% hint style="info" %}

#### Notes:

* Requires GPS data to be recorded in the ‘Configuration.’
  {% endhint %}

The ‘Events tab’ lists all the events recorded on the selected trigger, providing information such as the Logger and VIN for the event and the ‘Vehicle Structure’ used to record the event and the IVD file in which the event is recorded.


---

# 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.influxtechnology.com/support_guides/streamlog/streamlog-user-documentation/quick-start-guide/streamlog-operation/editors-tabs/events-tab.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.