> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/features/tips-and-hints/read-replicas.md).

# Read Replicas

This capability becomes particularly crucial when dealing with replication setups.

In such scenarios, Datasentinel displays distinct icons to easily distinguish between different components of the replication architecture: a <mark style="color:blue;">**P**</mark> icon for the primary instance and an <mark style="color:blue;">**R**</mark> icon for read replicas. This intuitive visual representation aids in quickly identifying and understanding the layout of your replication architecture.

<figure><img src="/files/Gx3SQqNrjmaKpZAI3R4c" alt=""><figcaption><p>Architecture example with a Primary and 2 Read Replicas</p></figcaption></figure>

Furthermore, by [tagging your primary and read replica instances](/manual/features/tips-and-hints/tags.md) with a common identifier, users can benefit from the [Consolidated View Feature](/manual/features/tips-and-hints/consolidated-view.md). This allows the analysis of the entire database architecture through a single, unified dashboard.

It simplifies the process of monitoring and managing multiple instances, ensuring that the health and performance of both primary and replica databases are within easy reach.

{% hint style="info" %}
For a deeper dive into how Datasentinel enhances database monitoring, refer to our detailed blog post: [High-Availability Cluster Monitoring with Datasentinel](https://blog.datasentinel.io/post/ha_cluster/).

This post elaborates on the practical applications of Datasentinel in real-world scenarios, demonstrating its effectiveness in analyzing complex database environments.
{% endhint %}


---

# 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://docs.datasentinel.io/manual/features/tips-and-hints/read-replicas.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.