This article provides brief information and steps to set thresholds and alerts to better monitor custom trigger events.
All STM versions
Alerts in Profile:
I. Create a Threshold rule:
1. Click Settings > Threshold Rules > Add New Rule > Threshold Rules.
2. Create this rule for Resource and the Category you want to alert on, and then click Save.
II. Assign the rule to the resources via Polices:
1. Click Settings > Policies.
2. Edit the policy that applies to the rule created. For example, if this is a rule for a Netapp filer, edit the NetApp Filer Policy. General threshold rules will be in the OS Policy.
3. Edit the Policy and then click Rules.
4. Move the new rule from Available to Selected and click Save.
5. Verify the Resource is assigned to this policy by clicking Resources.
6. Click Push when done. This will push the policy to the relevant agents. This will also update the configuration files for that resource (netapp in this example).
Note: Next you can verify the progress of the configuration push by clicking the Push List Report link in the top right corner. This will show No Data if the push has worked for the resource. You can also verify if any trap events are being received (assuming the thresholds have been met) by going to the web console > Monitors > Event Monitor.
These events are sent to the server from the profiler agents when a threshold is met. They can be edited to change any details of the trap going forward. For example, if you're seeing an event as Critical, you can edit this to reduce its priority.
III. Set Alert Notifications and assign Alert Email Notifications:
Now that you have confirmed Profiler is receiving traps, you can define which users will receive alert notification emails.
1. Configure the SMTP server by clicking Settings > E-mail.
2. Configure the User and email alerts in Settings > Manage Users.
3. Edit the user.
4. Define the Email Address.
5. Click Add beside Notifications.
6. Define which resource or group to apply to.
7. Define who the emails are sent to and determine the severity level of the event being sent.