PostgreSQL Suivi
Surveillez en temps réel les transactions, les connexions, la réplication et les performances de l'opération VACUUM de PostgreSQL, sans aucune configuration.
Pourquoi surveiller ? PostgreSQL?
PostgreSQL est la base de données relationnelle open source la plus avancée au monde, à laquelle on fait confiance pour les charges de travail critiques, des systèmes financiers aux applications géospatiales. La surveillance de PostgreSQL est essentielle pour détecter les requêtes de longue durée, éviter la saturation des connexions, suivre l'état de la réplication et optimiser les opérations de vacuum. L'intégration PostgreSQL de Xitoring offre une observabilité complète de la base de données.
Ce que nous moniteur
Active Connections
Number of currently active connections to the PostgreSQL server.
Transactions per Second
Rate of committed and rolled-back transactions.
Tuple Operations
Rate of inserted, updated, deleted, and fetched tuples across all databases.
Dead Tuples
Number of dead tuples waiting for vacuum, indicating potential table bloat.
Cache Hit Ratio
Percentage of data requests served from shared buffers without disk access.
Replication Lag
Bytes or seconds behind the primary in streaming replication.
WAL Generation Rate
Rate of Write-Ahead Log data being generated.
Lock Waits
Number of queries waiting to acquire locks on database objects.
Temp Files Created
Number and size of temporary files created for query processing.
Database Size
Total disk space used by each database including indexes.
Idle in Transaction
Connections that are idle inside an open transaction, potentially holding locks.
Checkpoints
Frequency and duration of checkpoint operations.
Configurable déclencheurs d'alerte
Configurez des déclencheurs personnalisés dans votre tableau de bord pour être averti dès que les indicateurs d{name}s dépassent les seuils que vous avez définis.

Active Connections
crucialFires when active connections approach max_connections, risking new connection refusal and application errors.
Replication Lag
crucialTriggers when streaming replication falls behind, risking data inconsistency between primary and replicas.
Dead Tuples
avertissementAlerts when dead tuple count grows beyond threshold, indicating vacuum is falling behind and table bloat is increasing.
Cache Hit Ratio
avertissementFires when cache hit ratio drops below threshold, indicating excessive disk I/O and potential memory pressure.
Lock Waits
avertissementTriggers when queries are blocked waiting for locks, indicating contention that degrades performance.
Transaction Rate Drop
crucialAlerts when transaction throughput drops significantly, indicating a potential database hang or performance issue.
Importance of PostgreSQL Monitoring
PostgreSQL handles mission-critical data for enterprises worldwide. Without proper monitoring, table bloat, replication drift, and connection exhaustion can lead to data corruption, outages, and unrecoverable failures.
- Detect long-running queries and lock contention early
- Prevent table bloat with vacuum performance tracking
- Monitor streaming replication for data consistency
- Identify connection leaks before pool exhaustion
- Track WAL generation for storage capacity planning


Why Choose Xitoring
Xitoring delivers enterprise-grade PostgreSQL monitoring with zero-config setup. Our lightweight agent auto-discovers your PostgreSQL instances, starts collecting metrics in under 60 seconds, and integrates with your existing notification channels.
- One-command install — no complex YAML or config files
- 15+ global monitoring nodes for low-latency checks
- Unified dashboard for servers, databases, and uptime
- Flexible alerting via Slack, PagerDuty, Telegram & more
- Historical data retention for capacity planning & audits


Commencez par procès-verbal
Install Xitogent on your server
If you haven't already, install the lightweight Xitogent monitoring agent on your server.
curl -s https://xitoring.com/install.sh | sudo bash -s -- --key=YOUR_API_KEYCreate a monitoring user in PostgreSQL
Create a dedicated read-only user for Xitogent to collect metrics:
CREATE USER xitoring WITH PASSWORD 'your_secure_password';
GRANT pg_monitor TO xitoring;Enable the PostgreSQL integration
Use the Xitoring dashboard or CLI to enable the PostgreSQL integration with the monitoring credentials.
sudo xitogent integrateConfigure alert thresholds (optional)
Set custom thresholds for metrics like replication lag, dead tuples, or connection count to get notified when something needs attention.
Souvent a posé des questions
Commencer à surveiller PostgreSQL aujourd'hui
Configuration en moins de 60 secondes. Aucune carte bancaire requise. Statistiques complètes dès le premier jour.
Commencer l'essai gratuit



