Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

APM Advanced Alerts

I am currently monitoring some endpoints (servers) using ICMP and the APM port monitor (finger port monitor). I am setting some alerts for the TCP port response time of the APM monitor based on a given threshold exceeded. However, the endpoints don't have thesame TCP RT thresholds and so I created different alerts based on the Application name, threshold etc. under the trigger condition. Should it be the application name that I am using in the trigger condition or should it be the component name that I should be using to distinguish the different endpoints due to different thresholds? I set the type of property to monitor as APM Component but I don't know if I should also be using the Application name (example Server1 TCP monitor) or the component name (only available selection is finger port monitor) to distinguish the different nodes. For the ICMP it's easy because you can just use the node name but I am not sure of the APM. I used the finger port monitor template on all of them. Any thoughts?

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

If you've defined the warning and critical thresholds for the TCP Port monitors in the APM component monitors. either in the master template or the template as it's assigned to the specific node then you can use the APM:Application OR APM:Component property in the Advanced Alert Manager. If you haven't defined the warning or critical thresholds in APM at all and are relying solely on the Advanced Alert Manager then you'll need to use the APM:Component property to designate the specific component monitor type you want to alert upon..

Option 1 - Define Thresholds in your Component Monitors and Alert on Application Status

Option #2 - Define your thresholds within the trigger condition using APM: Component

Kenpachiz

Kenpachiz replied on 01-13-2012 8:12 PM

Hi,

I have multiple nodes I am monitoring and they are grouped based on department. I am trying to configure an alert per department that is based on a specific TCP port response time (this is built using the finger port monitor template). This is what I have setup in the advance alert configuration:

-----------------------------------------------------------

Type of property to monitor: APM: Component

Trigger Alert when all the following apply

Response time is greater than or equal to 100

Department is equal to Local

-----------------------------------------------------------

My question is, will the alert be triggered when the response time is greater tha or equal to 100 for any device listed under the Department Local? I think what is confusing me is the Type of property to monitor and the conditions applicable. If I select the type of property to monitor as component, does it have any restrictions as to what conditions I can use? For example Department in my case which is under Network Nodes > Custom properties > Department, this is under Network Nodes but the property to monitor is Component so will the condition Department is equal to Local even be applicable? Thank you very much.

aLTeReGo

The alert as you have it written is correct albeit very broad. This will alert you when any application has a response time equal or greater than 100 for the "Local" department". If you only have one application you're monitoring in the "local" department this is fine, but if you have multiple this may over alert you. If you want to narrow this down a bit I'd suggest adding another condition for application name and/or component name to the alert trigger to narrow down the condition a bit. Other than that it's fine and should work as intended.

aLTeReGo

Almost forgot, a great way of testing an alert under real-world conditions to see if the trigger actions are defined properly would be to define the trigger condition to something known to be true. In your case you could configure the response time for "equal to or greater than 0" zero. This should force the alert to trigger and you can test your alerting to ensure it's working properly. I.E. the correct department's monitored applications are the only ones that fired.