solarview · Technical specialist network tooling · ✭✭✭✭✭

Very good idea !

This can be a workaround indeed, when you have to generate an alert as result of an snmp-trap, and you want to alert on Traptype only. I got it working with an interval time of 15 sec. Sometimes it is nescessary to alert on a combination of a traptype with a trapdetail. Therefore you have to join the TrapVarbinds table as…

Maybe in combination with NCM information ?

I am wondering why customers outside of these country's: US, UK, and Canada | Germany | Australia cannot win anything in this challenge ? There are more developed country's ...;-)

Sorry about that, Alex, I will think about it next time!

I selected "None of the above applies" becasue this applies to nothing, but this was wrong...

It is about : Compliance Reportingwith Log & Event Manager LEM = SEM ?

I get a lot of complaints from users about this feature since we upgraded to Solarwinds 12.3. Before upgrading you could make reports in .pdf, .csv, .xls and .html formats. Now only .pdf is available. When you do an upgrade, you expect new features, not missing features... Is there a plan to restore this feature ?

This should be a standard field in the nodes table. A lot of node inventories are based on the serial number of a device. We now have build some custom pollers for the various vendors to retrieve this information. I don't understand that this still not available in NPN, for instance in the node details screen. So please…

This is a must if you want to track who has put a network node in maintenance, or in unmanaged state. In the IOC, users are requesting rights to see Audit events, this is only possible without when we give them also admin rights. That's a no-go Granular access management should be made possible to enable serious network…

In the meantime, I have found a workaround to overcome this. The ${containerID} is not available yet, but you can use the ${Caption} instead. This parameter contains the selected group in the Group Summary page.

nice quiz!

We are using Serv. Now and Jira for requests

Richard, thanks for your tips, in the SQL studio this "streamlined" query is working well again. I am now testing it in the adv alert manager. How can we "push up the log level to DEBUG on the alert manager" ? (I know where the logfile resides..)

the same for me...

Thanks Alex, I just removed my comment because of your solution ;-) Regards, Sef

I also got an X with the right answers...

I already made a feature request for this in 2014, some 30 people support that idea.. Sef

In principle a good idea. But what is causing a lot of misunderstanding is the fact that a interfacename, constructed by a concatenation of IfDescr · ifName, is static, and does not change when the ifName of the monitored interfaces changes on the device. Sometimes the description of a interface, that is carrying the name…

We too are processing snmptraps by the SQL-query workaround. We have defined some 30 different trapalerts in this way. I think this is giving unnescessary database load, because you have to access the database each minute, to do the 30 different query's. Snmptraps are event driven, I think the process should be working on…

I read: the store will live on, maybe it is a moment to review/globalize your delivery strategy ? (there are also a lot of customers outside the USA, Germany and the UK ... ) I am looking forward to that !

In the latest version of Solarwinds (NPM 12.3 and NCM 7.8) the SwisV3 can be used for adding nodes to NPM and NCM. Swisv2 is not used anymore!

Looks like a logical request, each department (group) has it's own wishes, more customization !

That should be included too !

OK, I didn’t read it well enough, I think. Thanks for your explanation. I already made a mistake this month… Regards, Sef Sent from Mail for Windows 10

When you are building this "select all" checkbox, maybe it is also a good idea to make it possible to select only the top-N in a multiline graph.. that would change data into information !

It will make live easier for our SolarWinds users

see this page: LA 2019.4 Release Notes

No nodes were found matching 'AZSJPWEB01V'. Maybe a typo ?

Thanks, Is this SQL alerting method officially supported by Solarwinds NPM ? We can use it then (as a workaround until the traphandling and syslog handling in NPM is completely state of the art .. )