> 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/analytics/explorer-for-iotquery/settings-and-configuration.md).

# Settings and configuration

Your **Explorer for IoT Query** instance requires management to deliver optimal performance. Configuration controls what data flows into your system and how efficiently your queries perform - like tuning a system to get the clearest analytical signal.

## Understanding your system's health

![](/files/Hdc3AmcRvcSS7vJE0QuF)

The **System Health** dashboard shows your instance's current operational status. Check these indicators before making configuration changes.

* **Database Healthy** confirms your data storage systems are responding properly.
* **Streaming Low** indicates current real-time data ingestion rates - this varies naturally based on fleet activity and operational hours.

### Performance metrics explained

* **Database Size** shows current storage utilization and grows as your fleet operates over time.
* **Open Connections** indicates active users or queries accessing your data - higher numbers during business hours are normal.
* **Inserts per Minute** reflects real-time data ingestion from active vehicles - rates vary based on fleet operational patterns.

## Configuring data processing

Your **PTL Configuration** panel shows your **Dealer ID** and **Client ID**, confirming your **Navixy** account context.

### Historical data loading

This feature is provided on demand. Use **Run History Load** when automatic synchronization encounters issues or after changing data processing settings. The slider ranges up to 30 days - choose timeframes that represent meaningful operational patterns for your analysis.

Larger timeframes provide more historical context but require more processing time and storage. Processing runs in the background with progress shown in the upper-right corner.

### Optimizing data categories

Control which telematics data types your system processes to balance performance with analytical capabilities.

### Data category selection

* **Tracking Data** (always enabled) provides GPS coordinates, speed, and movement events - the foundation for all fleet analysis.
* **Inputs** captures sensor readings like fuel levels and temperature - enable for maintenance analysis and operational monitoring.
* **States** records device status including ignition and operational modes - useful for detailed activity analysis.

### Choosing your configuration

| **Configuration** | **Query response** | **Storage cost** | **Use case**           |
| ----------------- | ------------------ | ---------------- | ---------------------- |
| Tracking only     | Fast (1-2s)        | Low              | Basic fleet monitoring |
| Tracking + Inputs | Medium (2-5s)      | Medium           | Maintenance analysis   |
| All Categories    | Slower (5-10s)     | High             | Comprehensive analysis |

### Applying changes

Click **Update** to apply data category selections immediately. Changes affect future data processing - consider running historical data loading to apply new settings retroactively across your analytical timeframe.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/analytics/explorer-for-iotquery/settings-and-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.