The Mini DBA Connectivity Log shows database connection and data-access errors for one monitored server. Use it when a server connects intermittently, sampling fails, pages are empty, authentication breaks, or a database platform reports network, TLS, timeout, permission, or login errors.
What The Connectivity Log Is For
The Connectivity Log is different from the general Service Log. Service Log shows engine-wide startup, licensing, sampling, alerting, and background task messages. Connectivity Log focuses on one monitored database server and captures connectivity-related messages emitted by SQL Server, Azure SQL, PostgreSQL, MySQL, MariaDB, or Oracle data-access code.
Use Connectivity Log to answer questions such as:
- Is the Mini DBA Engine reaching the database host?
- Did the database reject the monitoring login?
- Is a timeout, TLS, certificate, DNS, firewall, or listener issue visible?
- Are individual platform queries failing after the connection succeeds?
- Is the issue happening repeatedly or only during a short incident window?
Open The Connectivity Log
- Open the Servers panel in the left console navigation.
- Right-click the monitored server node.
- Select Connectivity Log.
- Review the modal for recent connection, authentication, timeout, and data-access messages.
- Select Refresh after retrying the connection or waiting for another collection cycle.
- Select Close when you are finished.
The log is requested from the connected Mini DBA Engine service. In MSP mode, make sure the selected engine is the engine that owns the monitored server. A server on another engine has its own Connectivity Log on that engine.
What To Look For
Look for the first error in the time window, repeated errors, and messages that name the affected server, database, listener, endpoint, login, or SQL statement. A single transient timeout may be less important than repeated login failures or a consistent network error.
Common clues include:
- Login failed, access denied, invalid password, disabled login, or missing database user.
- Connection timeout, network path failure, listener refusal, DNS failure, or blocked port.
- TLS, SSL, encryption, trust, or certificate validation errors.
- Missing permission messages after the connection succeeds.
- Platform-specific errors from SQL Server DMVs, Azure SQL views, PostgreSQL extensions, MySQL system views, or Oracle dictionary views.
Empty Logs
If the modal says Log Empty., it usually means Mini DBA has not recorded a connectivity message for that server, the log has not been created yet, the wrong engine or server was selected, or the log was rotated or removed. An empty Connectivity Log does not prove the server is healthy; compare it with Service Log, Web Log, and the platform-specific connection guide.
Log File Location
The console normally opens the log through the Mini DBA Engine service, so users do not need file-system access. Administrators can also inspect the engine files directly when they have access to the Mini DBA Engine host.
| Deployment | Typical connectivity log folder |
|---|---|
| Linux service or container | /var/lib/minidba-engine/Logs/ConnectivityLogs/{InstanceType}/ |
| Windows service | C:\ProgramData\MiniDBA Engine\Logs\ConnectivityLogs\{InstanceType}\ |
| Azure App Service | %HOME%\site\data\minidba-engine\Logs\ConnectivityLogs\{InstanceType}\ |
{InstanceType} is the platform folder, such as SqlServer, AzureSql, Postgres, MySql, MariaDb, or Oracle. The file name is based on the monitored server name after Mini DBA maps it into a file-safe name. Older engines may also have fallback connectivity log folders directly under the engine app data folder.
Security Guidance
Connectivity logs can include host names, database names, login names, SQL error messages, and sometimes query or platform details. Do not share raw log extracts publicly. Remove passwords, secrets, connection strings, customer identifiers, API keys, and sensitive query text before sending log content to support or another team.