Overview of policies
TrueSight Middleware and Transaction Monitor includes a set of out-of-the-box policies that contain general monitoring recommendations. These policies can be used "as is" if you just require basic monitoring and want to get up and running quickly.
However, because every environment is unique, the supplied policies can also be tweaked to suit your requirements. You can also create your own policies.
For further details of how policies work, see Getting started with policies and Event Packs overview. For more advanced information on how policies are designed and their structure, see Policy architecture.
How are policies used?
Once the product has been installed, the policy for the relevant technology and platform you want to monitor can be selected from the list of out-of-the-box policies supplied with the product. Note that if you are monitoring technologies other than WebSphere MQ and the self-monitoring policies for TrueSight Middleware and Transaction Monitor (prefixed with BMM), you will need to import the relevant Event Pack - Event Packs are importable files of the relevant libraries and policies for the various platforms supported by TrueSight Middleware and Transaction Monitor.
The next steps in using a policy are to define the level of monitoring (from Minimal, Basic, Standard_NNN, or ALL_NNN - see Getting started with policies for more details on these levels), and then to copy and enable the policy. Once enabled, you can apply the policy to your existing objects.
Why and when?
Because the policies supplied with TrueSight Middleware and Transaction Monitor have been developed to address almost all basic monitoring needs, they are suited to getting up and running with your monitoring tasks within TrueSight Middleware and Transaction Monitor. As you become more familiar with the product, you can modify the policies, or you can create your own policies.
Policies are defined in the Policies tab of the Monitor Console, enabling the dynamic configuration of objects based on sets of expressions and actions through the UI.
Who can define and implement policies?
Typically, the product administrator defines and implements policies, although any user with the following two required permissions can see the objects in the Policies tab or perform actions on them:
- Access Policies Tab
- Edit Policies