Datasentinel Docs
Visit our websiteBlogRelease Notes
  • 👋Welcome
  • 🆓Free Trial
  • 📣Release Notes
  • Getting started
    • Architecture
    • Installation
      • 🌐Platform
      • 🕶️Agent
    • PostgreSQL clusters
      • 🔌Extensions
        • 🔌pg_stat_statements
        • 🔌pg_store_plans
        • 🔌system_stats
        • 🔌pg_buffercache
      • 🕶️Monitoring User
      • ➕Adding Connection
    • FAQs
      • ❓Platform FAQ
      • ❓Agent FAQ
  • Features
    • Key Features
      • 📊Session History
      • 📊Top Queries
      • 📂Top Tables
      • 🔓Lock Explorer
      • 📈Cluster & System Metrics
      • ⌚Live360
      • 📰Reporting
      • 🔔Alerting
        • Settings
        • Templates
        • Silences
        • Manager
    • Other Features
      • 📡Agentless Monitoring
      • 🛡️Role Based Access
      • 🔂Changed Parameters
    • Tips & Hints
      • 🖥️User Interface
      • 🏷️Tags
      • 🔀Metric Correlation
      • 👁️‍🗨️Consolidated View
      • ❗Graphical Annotations
      • ☁️Predefined Providers
      • ❓Wait Event Description
      • ®️Read Replicas
      • 👁️‍🗨️Agentless & System Metrics
      • ☑️Simplified pg_instance Display
  • implementation
    • Platform Usage
      • ⚙️Configuration
        • 🔑License
        • 📓LDAP
        • ✉️SMTP
        • 📋Audit
        • 👨‍🏭Users & Roles
      • 🧩API
        • 🔗Access Token
        • 🧩Connection API
        • 🧩Role API
        • 🧩User API
        • 🧩Reporting API
        • 🧩Workload API
        • 🧩Alerting API
      • 🛠️Tooling
    • Agent Usage
      • 📣Release Notes
      • ⌨️CLI
      • 🧩API
      • 🗃️Collection Level
      • 🔬Internals
    • Upgrade
      • 🔄Platform
      • 🔄Agent
    • Troubleshooting
      • 🩺Error message: “502 Bad Gateway”
      • 🩺The UI is not displaying any metrics for my new instance.
      • 🩺UI dashboard is encountering loading errors
      • 🩺InfluxDB
  • Support
    • How to Contact Us
  • GitHub Toolkit
Powered by GitBook
On this page
  1. Features
  2. Tips & Hints

Read Replicas

Datasentinel offers efficient monitoring of PostgreSQL Read Replicas through read-only access. It supports both local agent-based and agentless setups, ensuring flexible and seamless integration.

PreviousWait Event DescriptionNextAgentless & System Metrics

Last updated 1 year ago

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 P icon for the primary instance and an R icon for read replicas. This intuitive visual representation aids in quickly identifying and understanding the layout of your replication architecture.

Furthermore, by with a common identifier, users can benefit from the . 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.

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

For a deeper dive into how Datasentinel enhances database monitoring, refer to our detailed blog post: .

®️
High-Availability Cluster Monitoring with Datasentinel
tagging your primary and read replica instances
Consolidated View Feature
Architecture example with a Primary and 2 Read Replicas