qle ✭✭✭✭✭

Until SolarWinds fulfills your request, one option you have would be to manually recreate the AcknowledgeURL. For node alerts, it would be: host.solarwindsserver.com/.../AckAlert.aspx For interface alerts, it would be: host.solarwindsserver.com/.../AckAlert.aspx For volume alerts, it would be:…

Have you considered monitoring by IP address instead of hostname or is that something you're looking to avoid? Feel free to straighten me out if I sound a little confused here.

There is no log that stores alert activity. Instead, it's stored in the database, in the AlertLog table. You might be able discern the source of the problem by browsing that table. I'm guessing that it may be the account under which the SolarWinds Alerting Engine runs. Like all the other SolarWinds services, the SolarWinds…

I don't really have a suggested answer. I'm just curious about the integration between NPM and your external program. So does NPM test for connectivity to your e-mail servers and the Internet. Then, if either are down, it'll launch your external program which is preconfigured to send e-mail using an alternate e-mail server?

If anything, I imagine it would complement the recovery actions. Since the recovery actions are usually executed immediately, you can have the trigger delayed for a couple of minutes. If the service is still down, the alert will trigger. Then, you could have the the alert action repeat its attempt to restart the service at…

To sort, simply add order by <column name> to the end of the query. Here is the updated query with InterfaceAlias added. select n.nodeid, n.Caption as NodeName, i.InterfaceName, i.InterfaceAlias, InterfaceLastChange, i.Status, i.StatusLED from nodes n inner join interfaces i on n.nodeid = i.nodeid order by InterfaceAlias

Well, you *could* just stop the Alerting Engine service which would essentially disable all advanced alerts.

Following branfarm's steps to view the source, you simply have to search for the section that begins with: <select class="ReportDetails" name=drpdown onchange="window.open(this.options[this.selectedIndex].value);this.selectedIndex=0"> blah blah blah </select> You should find this section just a few lines before the section…

Since you have the OIDs, have you already created the UnDP pollers? If so, go ahead and create the alerts that you need for each statistic. If you have any trouble with the alert(s) not working properly, let us know.

Have you installed the MySQL Connector/ODBC (aka ODBC driver) on the NPM poller?

Ok, I understand. Yeah, I don't think that the User Defined Link resource supports variables. Just tested it with a few different variables and nothing. That was the bad news. The good news is that I was wrong in my first response, sorta. One of the new features of v9 is the support for variables in the Custom HTML…

Oh, I guess I got confused by your original post. If CSS11503 and CSS11506 aren't the servers, what are they and what servers are actually rebooting?

One of the easiest ways of integrating HEAT with NPM would probably be through the use of ATG. Identify events that you would like to track and create alerts that would send an e-mail to ATG. Provided the e-mail alerts conform to the ATG standard, you should start seeing some tickets being auto-generated.

* Until SolarWinds implements this, you could create a pseudo alert ID that's formed from the combination of two or more macros such as NodeID and AlertTriggerTime. It might not be pretty but it could possibly work. If you're willing to pull directly from the SQL database, you could also combine ActiveObject and…

What are the size of your icons? I believe something like this happened when the icon was too big/wide to display properly.

Yeah, this should work. Just make sure you set the trigger condition to execute when the the node status is not up as opposed to simply being down. This should cover all cases when the node is not up, which includes warning, unmanaged and unknown status.

Have you considering using the "Node List - Custom Grouping and Filtering" resource?

When an Advanced Alert is in a tripped state, does the alert engine look at the Trigger Conditions or does it just look at the Rearm Conditions? I apologize if I'm a little slow here but what are Rearm Conditions? Is this a new feature in NPM v10?

See if the following thread helps your situation. Removed interface still showing in SolarWinds

Here's a recent blog post that might better explain what's going on with NTA after certain intervals. Data Aggregation and Summarization for NetFlow (NTA)

I should've qualified my answer by indicating that we're running Spotlight for SQL Server. If you're not running this edition of Spotlight, I'm not sure how accurate this information would be for you.

Yeah, it sounds like an upgrade is in order. I can only assume it was introduced with APM 4.

Well, except for clearing the cache, I'm not sure if there's anything else to do. Sounds like you setup account limitations correctly. Is this option not working on any of your maps?

Have you already tried to define the alert with both trigger thresholds as well as DNS Hostname(s)?

Sure, it shouldn't be any different than what you're doing now. Just simply replace the Weather Channel map with the NWS animated map. Just use the URL specified in aLTeReGo's post earlier.

If you view the APM Application Details of an application monitor, you should see it in the upper-right, which is the default I believe.

Why not simply customize the thresholds either for the entire application monitor template or this specific assigned application monitor? If this a normal occurrence, it makes sense to customize the template or monitor to your own environment.

Have you created application templates and assigned them to nodes already? If so, you might be better served if your set your trigger alert to something like Application Name is equal to <your application template name> Application Status is not equal to Up Now, since you're on UNIX, APM will monitor the processes through…

Ah, good to know. Thanks for taking the time to update us.

I don't disagree with you but unfortunately, this is how it is currently. SolarWinds obviously needs to develop the concept of group alerts further.