User goals and features
The TrueSight Middleware and Transaction Monitor (TMTM) product provides you the capabilities for addressing the following business goals:
Description and references
|Understand trends and locate performance bottlenecks using history data|
TMTM enables you to collect history data using the History tab of the Monitor Console. The history database stores this history data as raw (high-resolution) and summarized (low-resolution) values of attributes, where they are available for querying and generating reports (you can also generate standard daily, weekly, or monthly reports for the properties of a selected object).
Once history data is collected, you can use it to understand trends via a trend chart in a real-time view. The trend chart graphs the value of one or more properties over time; there are a number of trend charts in the out-of-the-box physical views, particularly for key performance metrics. In logical views, it is useful to have trend charts comparing the values of a key attribute from multiple artifacts like the chart shown in the example view below that compares the average elapsed time between the various steps in a transaction pathway. This allows you to quickly see which step is the performance bottleneck (shown below in the yellow line, Back End).
When a chart in a logical view is opened, the TMTM Application Service subscribes to the current value of the topics on the chart and begins updating the chart in real time with new publications as long as the view remains open. In addition, the Management Console also makes a direct query to the history database to return past values of the topics. If there is no history, of course, no values will be populated, while any new values will populate.
Trend charts display data for a fixed interval into the past. To dynamically adjust the range of the chart to zoom in on particular problem times or to view a longer term trend, you can add separate buttons to the view that act on the chart in order to shift the viewing window backwards and forwards in time. See Working with views and dashboards for further information.
|Reduce the time for problem resolution by providing the relevant information in dashboards|
Dashboards help avoid the time needed to log in to multiple systems to look at different log files, screens, etc, in turn reducing the time to problem resolution. With all the relevant objects and properties collected in one view (a dashboard), the typical application user has everything required for their job role (including application performance analysis, health assessment, and recovery) on one screen across multiple platforms (whether distributed or mainframe).
A dashboard can show attribute data for many different types and type instances simultaneously; the dashboards required depend on the TMTM implementation and user needs for data visibility. For example, you can create a dashboard:
In general, dashboards can be customized to contain:
Use the Dashboard Wizard to intuitively create and modify dashboard templates, which are used to create dashboard instances.
|Simplify and automate monitoring with out-of-the-box policies|
With the need for automation ever-prevalent, TMTM enables you to apply a number of out-of-the-box monitoring policies to your environment, whether it be a production system or development and testing systems. These policies allow the dynamic configuration of objects based on sets of expressions and actions that are configured in a policy. And because every environment is unique, you can easily copy and tweak the supplied TMTM policies; you can also create your own policies.
Policies are defined in the Policy tab of the Monitor Console, and are comprised of the following key elements:
These elements can be combined together to form an automated monitoring policy, which can include, for example:
"Every Monday, at 2am, run discovery on agents with a "Production" role"
For further information, see Defining policies.
BMC has developed libraries of recommended event triggers used in each policy for each of the supported monitored technologies. However, only the event triggers that apply to IBM WebSphere MQ (MQ) and the self-monitoring event triggers are included by default in the Monitor Console. The libraries (and policies) for other supported middleware technologies are separated into an importable file called an Event Pack.