mark.mullens1 ✭✭✭✭✭

We use GNS3, WireShark, Systrack, Splunk and SCOM,

Oh and VM Tools

Yes, I agree and that won't be an issue for this situation. We already have good monitoring on all of those individual components. Our goal was to use a Group is Down / Group is Up alert that would trigger a slack message to let people know that an entire critical application is down. Anything else regarding the details…

Thank you. Not being a Tomcat guy myself I was unsure how the output for statistic thresholds was being calculated. I was able to use the custom conversion formula to ${Statistic}/1073741824 so the 3221225472 can be translated to 3GB. Thank you for clearing that up. !

Thank you, I'll work on this and see if we are able to obtain the results and behavior we are looking for. I will let you know how it goes and mark the answer accordingly.

Here is one of several we use in our NOC.

Hi anglia-admin, Here is what we currently use in our Group alerts. ALERT: ${N=SwisEntity;M=Name} is ${N=SwisEntity;M=Status;F=Status} <br> ${N=SwisEntity;M=Name}'s status has currently been ${N=SwisEntity;M=Status;F=Status} for ${N=Alerting;M=DownTime} minutes. <br> Root Cause: <br> ${GroupStatusRootCause} Which looks…

Has there been any improvements in this? I have tried the X/Y fix to only be bitten in the rear because it does no actual validation at that point. Does anyone have a better way to keep random transactions from showing false element/span/div/etc not found or as down?

Does it occur at a point in the transactions where you select anything from a back end database or authentication? I have seen this happen when I was recording a site where user name was selected from a list but behind the scene the selection triggered another URL to open in a hidden pop up. This hidden pop up's URL was…