The Service Log page shows log output from the Mini DBA Engine service. It is useful when troubleshooting engine startup, database connectivity, licensing, sampling, alerts, and background monitoring tasks.
When To Use The Service Log
Use Service Log when:
- An engine does not connect.
- A database server does not start monitoring.
- License activation or deactivation fails.
- Alerts are not being generated or sent.
- A platform page is missing data.
- The engine reports startup, validation, or sampling errors.
Use Connectivity Log instead when the question is specific to one monitored database server's connection, authentication, timeout, TLS, listener, or platform data-access errors.
How To Investigate
- Open Service Log.
- Choose the relevant log type if the page provides multiple log views.
- Look for errors around the time of the incident.
- Compare the error with the affected engine, server, database, or alert.
- Apply the fix, then confirm new log entries show recovery.
Common Log Clues
- License validation failures usually relate to serial keys, network access, proxy settings, expired licenses, or invalid license files.
- Database connection failures usually relate to network access, firewall rules, credentials, TLS settings, or database permissions.
- Sampling failures usually point to missing database permissions or unsupported platform features.
- Notification failures often point to email, Slack, Teams, PagerDuty, or Jira settings.
What To Capture From Service Log
When asking for help, capture the time of the issue, selected engine, affected database server, error message, and the action that triggered the log entry. For license issues, include the license action and engine name. For database monitoring issues, include the platform, server name, and whether a connection test succeeded.
Service Log is most useful when paired with the matching console action. Reproduce the problem, refresh the log, and compare entries before and after the retry. Avoid sharing secrets, connection strings, passwords, API keys, or customer-sensitive query text.
For server-specific database connectivity issues, right-click the monitored server in the tree and open Connectivity Log. Use Service Log for the wider engine context and Connectivity Log for the focused per-server error history.
Service Log FAQ
Is Service Log different from Web Log?
Yes. Service Log is engine-side. Web Log is console-side.
Why do old errors still appear?
Logs are historical. Use timestamps to confirm whether an error is current or already resolved.
What if no new log entry appears?
The request may not be reaching the engine. Check Web Log, engine connection state, endpoint, firewall, and proxy settings.
Related Pages
- Settings
- Licensing
- Connect database servers
- Connectivity Log
- Troubleshoot database connectivity
- Web log