qle ✭✭✭✭✭

If there was a variable for "alertdefid", I could do the same thing as the ack link. http://host.solarwindsserver.com/Orion/NetPerfMon/AckAlert.aspx?AlertDefID=${Alert.AlertDefID}:$[Node.NodeID}:Node&viaEmail=true Until an AlertDefID variable is made available and assuming your acknowledgement URL is correct, you might be…

See if the following entry in the Geek Speak Blog provides you some insight: Orion NTA and nProbe: Analyzing bandwidth hogs without flow-capable network equipment

Have you attempted to follow any of the aforementioned instructions to embed a utilization graph? If you can get one graph in there, it's very simple to setup the rest. As for NetFlow, I don't have that add-on module but I'm guessing the steps would be similar.

Why not test it by creating a new/another admin account?

Ok, let me see if I understand this correctly. You want a report that displays all nodes that went down within the last seven days (excluding Sunday) between 6AM and 9PM?

Ok, if it's just the same service you're looking to restart, couldn't you write a batch file/script to restart the service based on the IP address to pass to it?

Then you want to modify the All Down Events report. * Remove the Event Time and Message fields * Change Event Type Icon to Event Type and set function to COUNT Now it's just a matter of cleaning up the report a little like changing the column title for COUNT_of_Event_Type and deciding which column to sort on. Hopefully,…

The screenshot of your SWToolset.MenuOptions file doesn't show where you've inserted the line for Putty. Can you point it out?

If you have APM, you could also create a applicate template that queries uptime through WMI or the performance counter.

Sure, that's one of many ways you can refer to your nodes if you don't mind creating a trigger group and potentially adding a trigger condition for every node of this alert. If you have a standard naming convention, you might be able to refer to these nodes by their name as well. There are plenty of other fields you can…

That SQL query looks to be correct. The only thing that might possibly be wrong is the single quotes around the ${Nodes.NodeID}. Get rid of them so that it should look like the following: ${SQL:select distinct datediff(minute,e.EventTime,getdate()) from events e where e.NetworkNode = ${Nodes.NodeID}} Let us know if this…

* Do you have a link on the map that currently launches the "Engineering Notes"? * What's the name of the resource that you're using to display the map? Assuming it's "Network Map", that can be located in the (web site root)\NetPerfMon\Resources\7-1-NetworkMaps

Yeah, I ended up choosing a volume alert.

Any utility that would allow you to browse an SQL Server table should work but the easiest one to access would be the Database Manager includes with NPM.

If you based your templates off of their service name, wouldn't that make it easier to distinguish since they're usually unique on each server?

Oops, you're right, it should definitely be "Node Status is not equal to Down". I noticed that your second condition starts with "Application Status". What property are you monitoring? In my prior screenshot, you can see it towards the top as "APM: Applicaton".

Manually testing the alert will only test the trigger actions, not the trigger conditions. So you've assigned this application monitor to a node that you know has an error event within the last 140 minutes and it's still not showing as red (down) in APM?

This is the second thread ask for this capability. Advanced alert going from warning to down As far as I know, alerts cannot be configured to be dependent on each other. The only other way I can see this working is if the warning alert resets when the node status either up or down. This will only work if: * You use a…

My test alert is setup similarly to yours with a bunch of variables in the alert message. All of them are interpreted properly when the alert message is sent. What version are you running? Have you applied all of the appropriate hotfixes/service packs?

I'm not sure that all fields in all the tables have equivalent variables that can be used in the alerts. Anyway, AlertTriggerTime works great for the trigger action and DateTime should work as well. I'm probably not paying enough attention but from what I've seen, they usually provide the same output.

You should be able to simply disable the DirectLink account.

Clearly, the HTTP Form Login component is seeing two forms and can't figure out which is the correct login form. It seems that it unsuccessfully tried logging in using the first form. Perhaps you could configure the component to make an attempt on the second form to see if it has any success.

Bump. Just trying to figure whether anyone else can reproduce this on v9 or is it a problem with my installation?

Thanks for the suggestions. Tried both IP address and FQDN but still got the same results. Any other ideas?

Oh yeah! Any insight you can provide about acknowledging alerts through e-mail would definitely interest me. I know there has been interest in the past regarding the ability to acknowledge alerts via e-mail.

We're agreed on the necessity for testing. From my experience, when the interfaces and volumes show as unknown, they all go unknown.

I would like to get the report on the right as a summary like the one on the left so I can try to make a graph or chart. Where would the report on the left be in Orion it wasn't in the reports folder like the others? Alright, to make sure I'm understanding this correctly, you're looking for a report that lists the number…

I have some questions about this issue as well- I want to alert on any node being down, unless the router at the site is down, then I only want a single alert- for the router itself. If I have a site router down, I don't need a flood of email alerts to the on-call phone, I just need to have someone check on the site. This…

Ah ok, I wasn't aware of the remote machine. I have a suggestion for a different solution. I'm not sure how much more complex it is than your existing solution but hear me out. * Download and install AutoMailer on your remote server. * Configure AutoMailer to monitor a specific folder (such as c:\alerts) and use your…

I'm curious where you picked up the ${EventTime} variable. I couldn't find anything in the admin guide for it. What about testing it with either the ${AlertTriggerTime}, ${Time} or ${DateTime} variable?