Mini DBA Multi-Engine Mode

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Mode Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Performance History Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Multi-Engine Mode lets one Mini DBA Console connect to multiple Mini DBA Engine instances. It is designed for managed service providers, distributed DBA teams, multi-site organizations, isolated networks, and cloud estates that need one operational view without forcing every database server through one monitoring host.

When Multi-Engine Mode activates

Multi-Engine Mode activates automatically when the Console has more than one configured engine. Each engine remains responsible for its own database connections, sampling, alert generation, history, service logs, network access, and license state. The Console combines their data for cross-engine monitoring.

Common deployment patterns include:

One engine per customer for a managed service provider.
One engine per site, region, data center, cloud account, or subscription.
Separate engines for production and non-production.
One engine per network zone where firewall rules prevent central collection.
Separate engines for operational ownership, resilience, or maintenance boundaries.

Setup workflow

Install and start each Mini DBA Engine close to the databases it will monitor.
Open Settings in the Console.
Add each engine with a clear display name, endpoint, credentials, and auto-connect preference.
Test and connect each engine.
Add each monitored database server to the engine that owns it.
Use Server Groups to organize servers by customer, environment, region, platform, or owner.
Configure alert recipients, notification channels, and standard alert policies.
Open Enterprise View and Alerts to confirm cross-engine visibility.

Engine ownership

Every monitored database server belongs to one engine. That ownership determines where metrics and alert history are stored, which service log contains collection errors, which network path and credentials are used, and which engine license count is consumed.

Choose the engine with the correct network access, database credentials, host OS access, license capacity, and operational owner. Clear ownership also prevents same-named servers on different engines from being confused.

Engine selection and cross-engine views

The top-bar engine selector establishes the current engine context. The side navigation tree shows servers belonging to the selected engine, which is useful for focused investigation.

Use the global Alerts Current tab and Enterprise View when you need a combined view across connected engines. Use the selected-engine navigation tree, alert history, service log, and server-specific pages when investigating one estate.

Alert configuration across engines

From a server's Alerts page, Copy Config can copy an alert policy between same-type servers, including servers owned by different connected engines. Export and import are available when an engine is offline, air-gapped, or managed through a separate deployment process.

Before copying a policy between customers or environments, review notification groups, escalation routes, custom alert SQL, maintenance windows, and customer-specific thresholds. Copying configuration overwrites the target server's alert thresholds and notification settings.

Licensing

Each Mini DBA Engine has its own license. Activating, deactivating, or reviewing a license affects only that engine; the Console does not apply one engine license to all connected engines.

Community Edition permits one configured Community engine per Console. Additional Community engines remain visible but disabled. Licensed engines are exempt from that restriction.

Security

Separate Console access, engine access, and database monitoring credentials. Use least privilege for database monitoring users and avoid sharing customer credentials between engines. Engine and server names should make the customer, site, region, environment, or owner clear.

Troubleshooting

If an engine is missing from cross-engine views, open Settings and confirm it is connected. If servers are missing from the navigation tree, confirm which engine is selected.

If alerts are missing, check whether you are looking at the all-engine Current view, selected-engine history, or a server-specific Alerts page. Then inspect the Service Log for the engine that owns the server and the server's Connectivity Log.

FAQ

Does Multi-Engine Mode require a separate Console for each customer?

No. One Console can connect to multiple Mini DBA Engines. Each engine can represent a customer, site, region, environment, or network boundary.

Can I view current alerts from all engines?

Yes. Open Alerts and use the Current tab.

How do I focus on one engine?

Select it in the top-bar engine selector. The navigation tree and engine-scoped pages then use that engine context.

Does each engine have its own license?

Yes. Each engine has its own license state, expiry, and monitored-server allowance.