adatole ✭✭✭✭✭

The pricing list is probably your best source for understanding how each module is licensed. https://www.solarwinds.com/products/pricing

Here's some information from the current security advisory info. From here: https://www.solarwinds.com/securityadvisory/faq "What products are NOT affected by this security vulnerability?" "Our investigations are still early and ongoing, but based on our investigations to date, we have found no evidence that other versions…

Short answer: no inheritance. Medium answer: Orion user groups (whether orion-based, AD individual accounts, or AD groups) use an ACL-style structure. So when a user logs into Orion, whichever group they belong to which is highest up on the list when you go to "manage accounts" is going to be the rights they get every…

Detailed info on port 8099 can be found here: https://support.solarwinds.com/SuccessCenter/s/article/Change-the-internal-communication-port-used-by-TFTP-Server?language=en_US Upshot: "SolarWinds uses an internal communication port to communicate between the windows service and the various applications." The article I…

Linux CPU calculations (along with RAM calculations) are a many and splendorous thing - meaning the way you (or a particular utility, like top, htop, gtop, and more) calculate it has as much to do with how you feel about CPU/RAM as it does about the actual hardware. It's also why you can use Orion pollers (not to be…

You can find this answer in our Security Advisory FAQ (bolding and emphasis mine): https://www.solarwinds.com/securityadvisory/faq QUESTION 33 What products are NOT affected by the SUNBURST vulnerability? Our investigations are still ongoing, but based on our investigations to date, we have found no evidence that other…

You can find the full list of SolarWinds tools and modules that are (and aren't) affected here: https://www.solarwinds.com/securityadvisory (spoiler: ARM is not affected)

If you've applied the hotfix, then your alert trigger SHOULD be updated with the new variables. However, if it didn't, the new parameters are: <path to exe>\Solarwinds.APM.RealTimeProcessPoller.exe -n=${N=SwisEntity;M=NodeID} -alertID=${N=Alerting;M=AlertID} There are other parameters you can use (which you can find if you…

What I meant by "You are polling CPU (and other stats) every ?? minutes?" is what your actual statistic collection cycle is. Are you collecting stats every 5 minutes, 7 minutes, etc (also, are you collecting via WMI or SNMP. Per aLTeReGo's comment, the data is different depending on that choice). Because if you are…

Try it and let us know!

JoelGarnick: Glad your issue was resolve-able. I would definitely close the alert window before expecting it to pick up new custom fields you created in that utility (ie: not do both activities at the same time. YourVillageIdiot: Any update from that ticket? Just curious.

Clarify for me: You are polling CPU (and other stats) every ?? minutes? You are running the query trigger every 1 minute You are setting the delay (trigger when alert is true for more than) 15 minutes Your first alert runs the "top 10 processes" utility Your second alert emails after a 1 minute delay If that's true, 1)…

I second that emotion (that the alert manager in the upcoming NPM 11.5 would have helped you avoid this hassle). And I *have* tested this alert, and it DOES work. Beautifully. You really REALLY want to consider upgrading ASAP (remember, Release Candidates are fully supported by the SolarWinds production support group, and…

I looked back at your screenshot. You have a T+60 delay on the RealTimeProcess action, AND ALSO a T+60 delay for the email. That means the email is happening at the same time as the email. There's no time for the "get processes" task to execute before the email is sent. Remove the delay from the first task, and then add…

I've been doing some digging and haven't found any additional information. While the query as provided will list AP's that have been removed or are down, after a certain amount of time the WLC will "disappear" them, and at that point Orion can't list out the names of things it doesn't have. I can imagine a work-around of…

How often are you collecting CPU statistics. There's a logic gap in your timing. You can't ask for conditions existing for > 15 minutes if you are checking the alert every 10 min. By the time check #2 occurs, you are already 20 minutes out at best. Drop the "check alert every" back to the default 1 minute and see what that…

Thanks for this (and all the other) posts on this feature. One challenge we've run into is that over our very wide-spread environment, almost everything is a parent of something and a child of something else - with the exception of our very top level core equipment and our end-of-the-line devices. An example is: Orion…

In this case, what we want is very simple (or at least, a simple example, which we can build from there): I want to "select nodes.nodeid, nodes.caption, nodes.ip_address, nodes.city from nodes" I'm including city because I want at least one custom property, because I know (from doing this in Perl) that custom properties…

I'm clean out of ideas. Time to open a ticket! Please remember to come back to this thread and let us know how it turned out.

Good to hear, and I wasn't trying to imply that you weren't being respectful. I would definitely shift from emailing once a day to calling once a day. And you are 100% right, 30 days in the hole is unacceptable.

Thank you! But I believe DanielleH already it covered - it's called "MVP"! I hope many MANY more people join me in achieving that badge.

Put simply, the "test" button never works. It tests whether you CAN send an alert, but it doesn't populate variables AT ALL. Your better bet is to modify your alert in the following ways: * Add a "where" clause so it's limited to a single node (where nodes.nodeID = 123) * Change your thresholds so that ANY PC can trigger -…

Are you making sure you execute the program to get the processes SolarWinds.APM.RealTimeProcessPoller.exe -n=${NodeID} -alert=${AlertDefID} -timeout=60 In my post above, it was bullet-ed with an "A. " before it. Also, you have to make sure you put the PATH to that executable (SolarWinds.APM.RealTimeProcessPoller.exe) if…

I just want to second Jfrazier‌'s idea. by adding the script commands within the snmpd.conf file to respond to OID 9.9.9.9.9.9.9 (or whatever), you keep all the processing local and you also only execute the check whenever you poll that value. You can also control which user executes that script command and ensure it ONLY…

Thanks for the shout-out, HolyGuacamole . That article is an oldie but a goodie!

Would he accept an unsolicited opinion?

Are you collecting the metric named "Win_Processor_Queue_Len" for that node? (spellling counts, cApiTaliZatioN counts). If not, that's why you are getting the error.

The test button is nice (I almost wrote "cute" but I know aLTeReGo​ would hunt me down and kill me) but the reality is that you need to test REAL alerts with the entire flow. This is why your first alert action should be something like "log to file" (no, not email. NEVER EMAIL.). That way you can test it to your heart's…

Adding my voice to the mix. Running Orion Core 2011.2.2, SAM 5.0.1, NPM 10.2.2 We must use the "port http/80 forwarding to https/443" configuration for compliance reasons, so I can't use any of the UCS API aspects until this is resolved. Any movement on this?

Can you send me a screenshot of the alert trigger, and the alert trigger action? That will help me dig deeper into this.