Terminology
| Term | Meaning |
|---|---|
| DBaasNow | The company that develops Lifecycle Manager |
| Lifecycle Manager | A product developed by DBaasNow for provisioning, monitoring and managing database services |
| DBaasNow Lifecycle Manager | The full product name; Lifecycle Manager is its shortened name in this documentation |
| Gateway | Product component for reverse proxying and HTTP routing, with TLS termination and optional load balancing according to the deployment |
| Broker | Customer console for provisioning, administration and operation review |
| Plugin | Component that performs database operations on managed hosts |
| Monitor | Component that provides host/database health, performance and alerts |
| Repository | Central schema for lifecycle metadata and configuration, including access, licence, inventory and operational records |
| Coordinator | Component for distributed coordination, leader election and shared cluster state where implemented |
| Lifecycle Manager host | Host running server-side Lifecycle Manager services according to the approved deployment; DNCollector runs on target hosts |
| Target database | A customer PostgreSQL, MongoDB or Neo4j database onboarded for monitoring or provisioned through Lifecycle Manager |
| Target database host | Server running a target database and its DNCollector collection agent, on-premises or in the cloud |
| OS package repository | Source of operating-system software packages used during host preparation; separate from the Lifecycle Manager Repository |
| Project | A named database deployment in Lifecycle Manager, with its hosts and a dashboard for monitoring and available administration actions |
| Onboarding / promotion to monitoring | Bringing a discovered existing database into Lifecycle Manager for project-level monitoring |
| Day 0 / Day 1 / Day 2 | Preparation / initial delivery / ongoing operations across the database lifecycle |
| Catalog | Database services available under the activated licence |
| Request | A submitted operation |
| Execution | One attempt to perform an operation |
| Activity | Recorded progress, result and operation history |
| Standalone | A deployment with one database member |
| Cluster / replica set | Related database members providing replication or clustered service |
| Primary / leader | The member responsible for writes or database leadership |
| Standby / secondary | A replicating or read-serving member, depending on the engine |
| Plan Conversion | Changes the project's catalogue plan |
| Switchover | Planned change of the writer or leader |
| Failover | Leadership transition after a failure |
| DNCollector | Agent on target servers that collects host/database metadata and service status, and sends updates to the Broker; see the DNCollector operations |
| Activation Seed | Installation identity used to issue the matching licence key |
| Activation eKey | Issued key entered on License Activation |
| Decommission | Retirement of a managed database project |
| Uninstallation | Removal of platform components |
Database state, collected information and monitoring freshness are separate observations. Check the relevant views together when reviewing an operation.