Product capabilities
DBaasNow Lifecycle Manager combines database delivery, administration and operational visibility in the Broker. These capabilities support both new deployments and the ongoing work needed to maintain database services.
The following overview describes what each capability is for. Use the linked operation guides for the exact UI controls, prerequisites and verification steps.
Prepare the environment
Platform administrators configure organizations, applications, users, service credentials and the server pool. These records provide the ownership, access and host information used by subsequent operations.
The Catalog presents database services available under the activated licence. An administrator reviews the granted technologies and capacity; the customer selects an available service when provisioning a database. DB Version Control identifies the database versions available for the environment.
See Administrator Guide, database catalogue and DB Version Control.
Discover existing database services
After Lifecycle Manager is installed in the customer's environment, Discovery scans existing database services so the customer can onboard them for monitoring. The target databases can be on-premises or in the cloud, provided the required network connectivity is available.
The workflow connects discovery to ongoing visibility:
- Scan: review existing database services within the configured discovery scope.
- Onboard: select the discovered database to bring it into Lifecycle Manager's monitoring.
- Collect: the DNCollector agent running on the target servers collects host/database metadata and service status after onboarding.
- Monitor: open the project's dashboard to review host and database configuration, versions and metrics.
- Notify: enable alert and notification rules using thresholds appropriate to the service.
Discovery includes scan settings, discovered records and job history. Follow the Discovery guide, Monitoring projects and Monitoring and alerting administration for the related workflows.
Provision new database services
Users access the Lifecycle Manager console through the Broker to provision database services enabled by the activated licence. The V3 guides cover PostgreSQL Community, MongoDB Percona and Neo4j Enterprise. Additional database technologies are planned for future releases; the available services in an installation follow its release coverage and licence grant.
The selected catalogue service defines the database offering and intended topology. The user supplies the target hosts, credentials and deployment information, including a Project Name, and submits the provisioning request. Follow Activity to review its progress and verify the resulting deployment.
A named project and its dashboard
Once the target databases are provisioned and monitored by Lifecycle Manager, a project dashboard is created for the named deployment. It gives the user a view of the project's hosts and databases, bringing monitoring and administration into one place.
DNCollector agents running on the target servers collect host/database metadata and service status. The dashboard presents host and database configuration, versions and metrics. Customers can enable notification rules that alert when their defined thresholds are met.
Administration from the same dashboard
Users with the appropriate administrative permissions can perform the engine's available actions through the project dashboard:
- Add or delete database nodes.
- Apply supported database upgrades.
- Follow database migration workflows.
- Perform a planned switchover.
- Create and manage database users.
- Create and manage databases using the engine's administration workflow.
- Start or stop database services, including cluster service controls where offered.
- Start or stop DNCollector services.
The exact controls depend on the database engine and project topology. MongoDB database creation is part of Create user, as described in its operation guide.
See Catalog and provisioning, project navigation and the first-project walkthrough.
Manage topology and planned changes
Lifecycle controls help a database deployment adapt to changing requirements.
| Capability | Operational purpose |
|---|---|
| Plan Conversion | Change the project's catalogue plan; follow the engine procedure for any separate member additions |
| Add DB Node | Add a database member to an existing project |
| Delete DB Node | Remove a selected member using the engine's topology checks and removal procedure |
| Switchover | Perform a planned change of primary or database leader |
| Database upgrade | Apply an approved minor database version update within a supported version family |
| Database migration | Follow the engine's staged procedure for moving database service to replacement hosts |
| Decommission | Retire a database project that is no longer required |
Use the PostgreSQL, MongoDB Percona or Neo4j Enterprise guide. Adding a host to the server pool makes it available for selection; adding a database node changes an existing project's membership.
Administer databases and access
Each engine provides controls suited to its database model.
| Engine | Administration covered by this guide |
|---|---|
| PostgreSQL Community | Create and delete databases; create, change and delete users; manage supported parameters; review extensions and confirm the installed release's change support and database scope before an extension change |
| MongoDB Percona | Create, change and delete users; select database access and roles; manage member and replication settings |
| Neo4j Enterprise | Create and delete databases; create, change and delete users; manage database leadership through the available controls |
For MongoDB Percona, database creation is part of Create user with the database name and role selection. Follow MongoDB users and roles and database administration.
Broker user accounts and database user accounts serve different purposes. Platform accounts determine access to DBaasNow; engine users determine access to the managed databases.
Control database and collector services
Service controls start or stop database services within the scope offered by the engine's UI. DNCollector has separate start and stop controls for host and database information collection.
Stopping DNCollector pauses collection; it does not stop the database. A database or cluster service stop affects the database service itself. Review the scope before submitting either operation.
See Database and collector service control.
Monitor health, performance and capacity
Project dashboards provide visibility for onboarded existing databases and newly provisioned projects. They present host and database configuration, version information, host metadata and metrics. Operators can review CPU, memory, storage, I/O and network usage alongside engine-specific database metrics.
These observations help a DBA investigate resource pressure, compare conditions around a change and understand replication or service health. Check the selected project, time range and collection freshness when interpreting a dashboard.
Customers can enable notification rules to alert on conditions that meet their defined thresholds. Use these rules to direct attention to resource usage or database conditions that need review.
See Monitoring projects and Monitoring and alerting administration.
Review inventory, reports and Activity
Reports provide database inventory, filesystem utilization, operating-system and kernel information, host specifications, patch observations and monitoring status. Activity records submitted operations and their progress and results.
Together, these views support operational handover and investigation. A reported observation should be considered with its timestamp and the current project state.
See Reports, Activity and request status and Change history.
Select the applicable procedure
Available actions depend on the licence, user access, engine, version and topology. The controls and checks are engine-specific, even where the business objective is the same.
Plan maintenance around database health, redundancy and application reconnect behavior. Use release coverage, release notes and the relevant operation guide when deciding how to carry out a change.
See the DNCollector operations for collection details and the separate metadata and metrics paths.