> 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/pt-br/guide/events-and-notifications/vehicle-efficiency.md).

# Eficiência do veículo

Monitore a eficiência do veículo com regras de alerta para status MIL da luz de verificação do motor, motor ocioso excessivo e alterações do nível de combustível pelos sensores.

O **Eficiência do veículo** Esta seção abrange regras de alerta que ajudam a monitorar o status do motor, o motor ocioso e o uso de combustível em toda a frota.

* [**Luz de verificação do motor (MIL)**](/docs/user/pt-br/guide/events-and-notifications/vehicle-efficiency/check-engine-mil.md): Alertas quando a Lâmpada Indicadora de Mau Funcionamento (luz de verificação do motor) é acionada em um veículo.
* [**Em marcha lenta excessiva**](/docs/user/pt-br/guide/events-and-notifications/vehicle-efficiency/excessive-idling.md): Alertas quando um veículo permanece em motor ocioso por mais tempo que um limite definido, usando a lógica da plataforma ou eventos de hardware.
* [**Mudança no nível de combustível**](/docs/user/pt-br/guide/events-and-notifications/vehicle-efficiency/fuel-level-change.md): Alertas quando o sensor de combustível detecta uma mudança significativa de nível, indicando reabastecimento ou possível furto.


---

# 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/pt-br/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.