The Web Log page shows Mini DBA Console log output. It helps troubleshoot browser console behavior, user session issues, settings access, UI errors, and calls from the console to connected engines.
When To Use The Web Log
Use Web Log when:
- A console page does not load correctly.
- A settings form fails before reaching the engine.
- A user cannot access Settings.
- The browser UI reports an error.
- Engine connection state in the console does not match expectations.
Web Log Vs Service Log
Use Web Log for console-side behavior. Use Service Log for engine-side behavior.
For example, if the Settings page cannot send an activation request, start with Web Log. If the request reaches the engine but activation fails, check Service Log.
For one monitored database server that connects intermittently or has sampling errors, use Connectivity Log. It shows per-server database connectivity and data-access messages requested from the selected Mini DBA Engine.
Troubleshooting Workflow
- Reproduce the console issue.
- Open Web Log and find entries at the same time.
- Check whether the error is browser, authentication, settings, or engine communication related.
- If the error involves an engine call, open Service Log for the same time period.
- Correct the configuration and retry.
What To Capture From Web Log
When reporting a console issue, capture the page name, browser action, time of the error, visible message, and relevant Web Log entry. If the issue involves saving settings, changing license state, or calling a connected engine, also capture the selected engine name and matching Service Log entries.
Web Log is especially helpful when a problem occurs before the engine receives a request. Examples include validation failures, authentication behavior, browser-side rendering errors, and failed calls from the console to the engine endpoint. If the engine receives the request but the action fails while executing, Service Log will usually be more useful.
Avoid sharing screenshots or log extracts that include secrets, API keys, passwords, or customer data.
Web Log FAQ
Is Web Log the same as Service Log?
No. Web Log is console-side. Service Log is engine-side.
Why does support ask for a time window?
The time window helps match browser actions, engine requests, alerts, and database collection events.
What if Web Log is empty?
Reproduce the issue, refresh the page if needed, and check whether the problem is happening in the browser, network, or engine.