Comments
-
There's no reason that email recipient "A" needs to be in all three alert actions. If they're in the first alert action then they'll continue to receive the email notification every 30min regardless. I am not certain I agree with you on that, they may need to be aware of who is getting notified in all stages of the…
-
I am not seeing anything that indicates a corrupt .sdf in the logfiles mentioned in the article. I will keep searching. On a slightly related note, I am scheduled to throw SAM6.0 & NPM10.6 on this week and starting to think that I should hold off on that. any thoughts?
-
I will accept that answer, though it isn't quite what I was getting at. Here is another question that may be more to the original question I was trying to ask. Is there a mechanism for stopping alerts after a certain time frame, i.e send email repeatedly every 30 minutes for 4 hours then stop sending emails? Reason for…
-
Thank you that is what I thought but I needed some confirmation.
-
It looks like this is the only way to accomplish that. Thanks
-
statistic.message: SQLException not found statistic.status: 0
-
in a word, yes.
-
Thanks but that didn't resolve the issue
-
Can this be set in a way to ignore all loopback addresses or network volumes so that they do not appear in future scans? Or will I need to cron a task to query the DB directly and make that change post-discovery?
-
HolyGuacamole wrote: Also, I am curious about this alert definition (Unmanaged - it is used to not get alerts. Unreachable - also used to not get alerts when a parent object in the dependency definition is down. But, you have these statuses in the trigger condition to actual get an alert - not sure why. We have done this…
-
SELECT DISTINCT APM_AlertsAndReportsData.ComponentID AS NetObjectID, APM_AlertsAndReportsData.ComponentName AS Name FROM Nodes INNER JOIN APM_AlertsAndReportsData ON (Nodes.NodeID = APM_AlertsAndReportsData.NodeId) WHERE ( (Nodes.Caption = 'dtord01hdp') AND ( (APM_AlertsAndReportsData.ApplicationName =…
-
That is what I thought, thanks
-
That was it, I assumed the test would scan the node and report on any of the disk volumes. Now I know better, thanks you
-
I believe the word I am looking for is 'derp' Thanks, I had completely forgotten about that
-
Thanks for the reply. I think I may not have communicated my question clearly. I have 3 actions that are set to take place when an event is registered, initial event email1, wait 30 min email2, wait 30 min email3. In the event that the alert is not acknowledged and it proceeds to the next step in the escalation process…
-
Thank you Petr, I will try this on my dev instance and let you know how it works.
-
That did it, thank you much
-
Any new news on IPv6, we are transitioning our entire environment starting 1-2014, with out support it may be hard to keep NPM or is there some where that I can find the information I need to support ipv6?
-
I am getting this during an Additional Poller install for NPM11.5.2/SAM6.2.1 at the compatibility checker portion
-
The Bar chart is a request from the higher ups. We have a dummy account that displays WAN link status, overall hardware health, active alerts, and Node Groups. For the NOC the pie chart is fine and actually works quite well in my experience, but for general display purposes the people that sign my check want the…
-
One other question, on alert suppression I would like to not be notified when our DEV servers are full or approaching full. I have all of our dev servers in a group named DEV/QA, I would like to exclude this group from alerting but can't seem to find a way to use the group is equal to DEV/QA in the suppression options.…
-
this seems to be resolved, a quick question regarding alerts. I have multiple alerts that I have configured for various potential issues. (I know this is a surprise to everyone) I test an APM: Hardware monitor alert on a box that I have offlined a drive on, the test doesn't seem to pick up this down drive is that normal…
-
Same result, I am at a loss as to where the disconnect is.
-
No joy, set the condition to >= 0 and tested against an active server
-
You would think the 95% mark would be hard to hit, but the app logging goes to /opt (yes, I know that is a poor design choice, no I do not have any say in the matter) and fills rather quickly. Also, the log rotation is not, how can I put this, well thought out. I will try lowering the threshold and test again. I will post…