DNCollector operations
DNCollector is the collection agent on the target database server. It supplies host and database information used by DBaasNow Lifecycle Manager to monitor database projects. It supports the monitoring workflows for PostgreSQL Community, MongoDB Percona and Neo4j Enterprise.
DNCollector is installed automatically as part of Discovery onboarding of an existing database service or provisioning a new database service. Customers do not install the agent separately.
DNCollector is one of the architectural components of DBaasNow Lifecycle Manager, alongside Gateway, Broker, Plugin, Monitor, Repository and Coordinator. DNCollector runs on the separate target hosts, which can be on-premises or in the cloud when the required connectivity is available.
Where DNCollector fits
| Responsibility | Component or service |
|---|---|
| Submit operations and view project information | Broker |
| Deploy and configure monitoring on target hosts as part of supported workflows | Plugin |
| Collect target-host and database metadata and service status | DNCollector |
| Receive collection updates and make project records available to customers | Broker and Repository |
| Provide host/database performance observations and threshold-based alerting | Monitor |
DNCollector and the metrics collection services work together to support monitoring. Metadata updates and performance charts follow different paths and can have different observation times. See Architecture.
Operating procedures
| Task | Procedure |
|---|---|
| Understand when the agent is installed and which connections it uses | Automatic installation and connectivity |
| Understand the collected information and update behavior | Collection and updates |
| Start or stop collection through the project dashboard | Service control |
| Check monitoring after onboarding, provisioning or maintenance | Verify collection |
| Investigate stale information and prepare a support case | Troubleshooting and support |
| Run installed-agent checks for a support investigation | Support commands |
Before you begin
You need access to the relevant project in the Broker. Service-control actions require the appropriate permissions. Coordinate target-host access and network checks with the server and monitoring administrators.
New database provisioning and existing database onboarding are separate entry paths. Follow Getting Started and the applicable engine guide. Discovery results must be onboarded for monitoring before you expect ongoing DNCollector collection.
Stopping DNCollector stops its ongoing collection and updates; it does not stop the target database service. Performance collection services may continue running separately. Check both metadata and metrics when assessing monitoring health.