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

# Vehicle efficiency

Monitor vehicle efficiency with alert rules for check engine MIL status, excessive idling, and fuel level changes from sensors.

The **Vehicle efficiency** section covers alert rules that help monitor engine status, idling, and fuel use across a fleet.

* [**Check engine (MIL)**](/docs/user/guide/events-and-notifications/vehicle-efficiency/check-engine-mil.md): Alerts when the Malfunction Indicator Lamp (check engine light) activates on a vehicle.
* [**Excessive idling**](/docs/user/guide/events-and-notifications/vehicle-efficiency/excessive-idling.md): Alerts when a vehicle idles longer than a set threshold, using platform logic or hardware events.
* [**Fuel level change**](/docs/user/guide/events-and-notifications/vehicle-efficiency/fuel-level-change.md): Alerts when the fuel sensor detects a significant level change, signaling refueling or potential theft.


---

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