Depending on the nature of a specific trace, the list of operations in the corresponding Trace Detail pane might be very long. Spring Insight uses smart collapse, which means it collapses those operations it thinks are unimportant but uncollapses operations which are most likely interesting to you. However, the Trace Details pane could still be very large. In this case, you might want to filter the list of operations so as to display only certain types that you are interested in.
The list of available filters depends on the plug-ins currently installed in Spring Insight as well as the type of operations in the current list of trace details. Spring Insight has a number of plug-ins installed by default. Click the Administration tab on the main dashboard then Collection Plug-Ins to see the list. If you have previously added your own custom plug-in to Spring Insight so as to display custom trace details, then this filter might also be available.
The default list of filters is as follows:
Database: Filters operations based on whether they are related to general database calls. This could include transactions as well as standard calls to a relational database, for example.
JDBC: Filters operations based on whether they are JDBC calls. The results of this filter are a subset of the results of the Databse filter.
Web: Filters operations based on whether they are related to Web calls, such as HTTP requests and responses, rendering of HTML pages, and so on.
Filters are tri-state—you can set each filter to one of three different states:
Unselected – operations are included in the results unless one or more other filters are set to + (plus)
+ (plus sign) – only these operations are included in the results
- (minus sign) - only these operations are excluded from the results
Filters are sticky, which means that they stay in place even when you navigate away from the page in which you set the filter. This is useful if you want to look at multiple applications or End Points, searching for JDBC calls, because you do not have to reset the filter each time you look at a different trace. You can remove the filter at any time, as described in the procedure below.
To use filters, follow these steps:
Display the Trace Details pane for a particular trace you are interested in. See Viewing Recent Activity of Your Application.
In the top-right corner of the Trace Details pane, click the Filter drop-down list and select the filters you want to apply. You can select multiple filters; the results are a sum of the individual filter results. Set the filter to + (plus) to include only those operations, - (minus) to exclude the operations, or leave the box unselected. If you do not set a filter to + or -, the operations are included unless another filter is set to +.
The preceding graphic shows how to apply a JDBC filter.
Click to the left of the Filter drop-down list to actually apply the filter. A message appears below the Trace Detail label that alerts that a filter is being applied.
After applying the filter, the trace details navigation tree should have gotten smaller, and the only details that are now included are those related to the specified filter, such as JDBC calls in our example.
Because of the stickiness of the filter, as you navigate away from your current page you'll see that Spring Insight continues to apply the filter.
To remove the filter, click on the
X to the left of
Filter applied to trace alert.