Monitoring projects
Project dashboards provide visibility for existing databases onboarded through Discovery and for newly provisioned database projects. They bring together host and database configuration, version information and metrics.
After an existing database is onboarded, DNCollector agents running on its target servers collect host/database metadata and service status used by platform monitoring. Open the intended project and verify the dashboard project/cluster selector.
| View | Purpose |
|---|---|
| Home | Project summary and metadata |
| Host-Insights | CPU/memory, filesystems and OS patch observations |
| Host-Metrics | Time-series CPU/load/memory/disk/I/O/network dashboards |
| DB-Metrics | Database version, role, service health and performance observations |
Use time-range and refresh controls; choose a range including the operation being investigated. Check collection timestamps before comparing observations.
Interpret metrics
Look at trends and topology together. A growing replication delay can indicate network/resource limits. An empty panel can indicate selection, collection or scrape failure. A leader change can be planned or election-driven.
For specific columns, use PostgreSQL monitoring, MongoDB monitoring and Neo4j monitoring.
Threshold-based alerts and notifications
Customers can configure alert and notification rules using defined thresholds for monitored conditions. Review the relevant host or database metrics when choosing a threshold, then verify that the rule and notification destination work as intended.
Use Monitoring and alerting administration for alert rules, contact points and notification policies.
Known display gaps
The supplied release notes report Ubuntu patch visibility gaps, stale deleted PostgreSQL panels and some Oracle Linux Neo4j insights gaps. Check the actual host/engine and collector before treating missing information as service failure or compliance evidence.
Deleting a node changes topology and monitoring targets; historical samples/panels may remain. See release limitations.
See the DNCollector operations for collection details and the separate metadata and metrics paths.