> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/es/guide/events-and-notifications/vehicle-efficiency.md).

# Eficiencia del vehículo

Supervise la eficiencia del vehículo con reglas de alerta para el estado del MIL de check engine, el Tiempo de ralentí excesivo y los cambios en el nivel de Combustible de los sensores.

El **Eficiencia del vehículo** Esta sección abarca reglas de alertas que ayudan a monitorear el estado del motor, el ralentí y el uso de combustible en toda la flota.

* [**Revisión del motor (MIL)**](/docs/user/es/guide/events-and-notifications/vehicle-efficiency/check-engine-mil.md): Alertas cuando se activa la luz indicadora de mal funcionamiento (check engine) en un vehículo.
* [**Tiempo de ralentí excesivo**](/docs/user/es/guide/events-and-notifications/vehicle-efficiency/excessive-idling.md): Alertas cuando un vehículo permanece en ralentí más tiempo que un umbral establecido, usando la lógica de la plataforma o eventos de hardware.
* [**Cambio del nivel de combustible**](/docs/user/es/guide/events-and-notifications/vehicle-efficiency/fuel-level-change.md): Alertas cuando el sensor de combustible detecta un cambio significativo de nivel, lo que indica repostaje o posible robo.


---

# 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://navixy.com/docs/user/es/guide/events-and-notifications/vehicle-efficiency.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.