> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/ion-analytics/slas.md).

# SLAs

Our analytics system replicates your ION data to a secure data warehouse environment so that you can create complex queries and aggregations that are commonly required for making custom reports and dashboards. This data environment is designed for these type of workloads. All changes within ION are replicated into the analytics environment, and we provide several tiers for tables within ION:

1. Base tables that are generated from the raw replicated data.
2. Enriched tables and data products which involve transformations of the data in order to provide aggregated and joined data.

The replication process will inherently have some delay between when a change is made between ION and when a change is reflected in analytics. ION analytics provides the following SLAs for getting your data within analytics:

1. Base table delay (the delay from capturing the raw changes from ION):
   1. We guarantee that the P99 base table delay will be within 5 minutes;
2. Enriched and data product delay (the delay from applying transformations to produce these tables):
   1. We guarantee that the P99 enriched and data product delay will be within 30 minutes.

### Data Integrity

Due to the nature of distributed systems, there is a non-zero probability that we may miss an update in replication process. We have incorporated checks within the system to detect missed updates, and make any necessary repairs by refreshing the state of your data.


---

# 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://manual.firstresonance.io/ion-analytics/slas.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.