> For the complete documentation index, see [llms.txt](https://docs.skyledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyledge.com/knowledge-base/articles/what-is-an-event.md).

# What is an Event

Events are real-time data points captured as a result of asset or vehicle usage. Their primary purpose is to notify the business of situations necessitating either logging for auditing purposes or triggering alerts for compliance and maintenance needs. All published events are associated with a parent template [event-type](https://docs.skyledge.com/knowledge-base/articles/what-is-an-event-type.md) class, which includes relevant metadata fields for streamlined event reporting.

Examples of asset-related events include:

* On and off triggers
* Threshold triggers (e.g., RPM, speed)
* Usage amounts (in minutes or distance)
* Alarms

It's important to note:&#x20;

* All events are asset-driven and can not be created manually via the platform console
* All events are linked to a parent event-type template that contains relevant metadata fields for comprehensive asset, business unit or organization reporting.&#x20;

<details>

<summary>Tags</summary>

Events are real-time data points captured as a result of asset or vehicle usage. Their primary purpose is to notify the business of situations necessitating either logging for auditing purposes or triggering alerts for compliance and maintenance needs. All published events are associated with a parent template [event-type](https://docs.skyledge.com/knowledge-base/articles/what-is-an-event-type.md) class, which includes relevant metadata fields for streamlined event reporting.

label: event stream, fuel, speed, brake, alert

</details>


---

# 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.skyledge.com/knowledge-base/articles/what-is-an-event.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.
