The web dashboard is the standard monitoring dashboard. Firstly, you will be directed to the first tab which is Instance Status. The Instance Status tab shows an overview of statistics and issues during monitoring.


Instances status displayed as visual representation are enclosed in circular shapes. Coloring coding consist of blue for lost connection, red for alarm, orange for warning, gray for not monitored and green for ok. Indicated inside for each distinct color are the number of database instances corresponding to the beforementioned statuses. Underneath it lists all available database instances for every status. Above it is distinct issues encountered after jobs are executed. Six notable fields are seen: Group, Instance Name, Task, Status, Status Time and Details.

Group is the group for this instances in dbWatch. Instance is the instance name / givenname for the instances in dbWatch, task is the name of the monitoring check / alert / task that has reported an error, status is the severity of the error, Status Time is the time this status has been raised, and details is a short description of the problem. The layout and information is configurable, but this is the default.

Proceeding with the next tab – Instances, you will see a table showing the status of every instances. This view lists all instances neatly organize and tabularized. Found on this tab are columns: Status, Name, Platform, Edition, etc. Noteworthy columns to be wary of are Disk Usage which checks the ROM, Activity Status Bar which shows the resource consumption and Status which indicates the abovementioned color scheme.


Example view, where no database instances are in status “Lost connection”

By default when you install dbWatch Server, the web server is not running. The webserver is enabled when dbWatch Server detects the webserver configuration file at startup. The configuration file, named http_configuration.xml must be located in the dbWatch config directory. By default, on Windows, for version 12.3.8, this directory would be “C:\ProgramData\dbWatch\12.3.8\server\config\”. This is the same directory where the other config files, such as authentication.xml and server_configuration.xml (and others) are located.

The basic contents of this file is:


That is all which is needed to get the basic dashboard up and running. It will now be located on http://localhost:8080/dashboard/index.html

Each of the fields on this dashboard has a name. The different balls (lost connection, alarm, warning and ok), are named “query_lost”, “query_alarm”, “query_warning” and “query_ok”. Then the list of issues is named “query_issues”.
If they are not spesified in the http_configuration.xml file, the defaults are used. If your configuration file looks like this:

8080localhostWARNING’ | status=‘ALARM’]->t/$t[enabled=‘YES’]/name\{‘Task’ \}/$t/status/id\{‘Status’ \}/$t/statustime\{‘Statustime’ #sort(desc) #renderdate\}/$t/details\{‘Details’\}”/>

The resulting dashboard would be identical, but now you you can see the queries as they are, and alter them if you need to.

← Dashboards and Overview Screens / Multiserver web dashboards →


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment