dbWatch 12.x has a greatly improved grouping and filtering mechanisms for quick navigation and unprecedented overview.
In the tree structure that you will find throughout dbWatch there are 3 components that lets you group and filter instances.
On the top you have the quick text based filter.
On the bottom you have a metadata filter and the group by component.
The text filter works by removing all branches of the tree that do not have a node matching the filter.
In the example below, we type in “Dem” and all instances except the one called “Demo Server” are removed.
The text filter is not restricted to instance names, all nodes in the tree are considered. For example typing “Bac” will remove all branches that do not contain that text. In our case that will leave only instances with an alert named something with “backup”, and also remove all other alerts.
When the tree is a “status tree” (statuses propagate in the tree), the filtering will also result in the propagated statuses changing. For example if an instance has 2 alerts, a backup alert with status warning and a disk space alert with status alarm, the worst status will propagate to the instance (in this case alarm). The if you type “backup” in the filter box, the disk space alert will dissapear and the instance status will change to warning.
The metadata filter is more powerfull than the simple text filter and allows you to filter instances based on all the properties available on the instance.
In the example below we state that only Oracle instances with a host containing “1.9” in their address should be visible.
The lines in the metadata filter correspond to filters that can used in Dbwql queries for instances (The part in the square brackets). Read more about Dbwql and its syntax.
To see all the available properties that can be used in the metadata filter, open the Dbwql Console (Available from the “Help” -> “Dbwql console” menu) and type “instance/” and press the tab key.
The group by component lets you define how your instances are grouped in the tree.
By default, the first node in the tree is the Server name, then group name, subgroup name (if any), then the servicegroupings (if any).
You can group by any property that is available on the instances.
This is an extremly powerfull feature that allows us to dynamically change the your entire view of your environment.
For example, we can remove all the properties (right click on them and click delete) then add “task” (type task in the textbox and hit enter or click “+”).
Now we see that our instances are grouped by what tasks they have installed. For example we quickly see that only 4 instances have the “Agent Jobs Check” installed.
In another example, we group by server and customer.
And we see that “sql 2016 b” belongs to “Customer A” and “sql 2016” belongs to “Customer B”. Also notice that instances that do not have a defined customer are grouped directly under the Server node.
Adding static metadata (like customer) to instances is done in the Configure instance view.
Adding dynamic properties to instance can be done using the Property system.