joedissmeyer

Thanks aLTeReGo‌ I appreciate it! To reply to your mention about the polling agent, yes we are testing that very agent in our environment and we hope to start implementing the agent in our more secure environments (such as our DMZs and other highly secure zones). So far testing has been positive and we believe we can have…

rstoney00, Now that is a great idea If you're cool with sharing that template on the content exchange, I'd love to give it a whirl in my environment. - Joe

Ah, I see. This is also a helpful answer, thank you alterego. I will give the template above a try and see how well that will work for us.

Thanks njoylif. I will give this template a try and let you know how it goes.

Leon Adato I wanted to let you know what I did so far. Using your example as a base, I pulled together this: select Nodes.Caption 'NODE NAME', APM_Application.Name 'APM NAME', APM_ComponentDetails.Name 'COMPONENT NAME', APM_ComponentDefinition.name 'COMPONENT TYPE', APM_ComponentDetails."Key" 'VARIABLE',…

Leon, Thank you very much! This is a great start. I wasn't sure where to begin but this query helps tremendously. I will mark this as the correct answer and build on this query to get more details per component. Thanks again! - Joe

Hi Jeff. I will try to help and answer this question without getting into detailed terminology or semantics I know exactly what you are asking. It is true that F5's are built with a Linux core. However, F5's are designed to work solely as a high performance network appliance which is the same category as a router, switch,…

Thanks for clarifying aLTeReGo. I appreciate it!

No I never thought of that! I didn't know about the SDK on Github. I'll see what I can do.

janene16‌, yes you are correct. The KB article is the correct answer. Thank you for sharing. So my question now is: Does SolarWinds count this as an "issue"? Or is this logic by design?

Thanks Alterego I appreciate it. I'll reach out to Adam.

Ok good to know. Next time this happens I'll give this a whirl. Thanks aLTeReGo

Thanks Jay! Your answer was the correct one. Here is what I did: Logged into the SW server and created a new Advanced alert. The "Trigger Condition" area is the important one. Here is what I have: Type of Property to Monitor: Custom SQL Set up your Trigger Query: Node WHERE ( (DATEDIFF(mi, Nodes.LastSystemUpTimePollUtc,…

Thanks Automag. I will give this a try and let you know if this solves the issue. - Joe

This is the correct answer. Clearing out the three tables listed above will effectively "reset" all of your Ignored Discovery items back to zero. After clearing these tables out you will want to allow your discovery jobs to run normally (or you can run them on-demand) and start rebuilding your ignore list from scratch.

Diner​ Jan, Just wanted to follow-up with what we did here. I did delete all of the rules listed in the old AlertManager.exe tool on our primary poller. However, it only listed the first 50 rules from the AlertDefinitions table. We still had well over 200 obsolete alert rules listed in the table. The only option from here…

Thanks Jan I appreciate the response. I'll go the recommended route using the AlertManager.exe tool.

Yes, under the trigger conditions tab in the Edit Alert screen, the "Do not trigger this action until condition exists for more than" option was set to '0' (zero) minutes. However, we did change this to 3 minutes, 10 minutes, and so on, but the application alerts still triggered. What I have done for now is omit our custom…

This exact step resolved our issue as well. Reinstalling the VS C++ 2013 redistributables resolved the issue. Issue: In my environment we have one primary poller with NPM and SAM, and three additional polling engines. One of the polling engines was not working. The "SolarWinds Orion Module Engine" service was stopped.…

Excellent solution! Thanks for sharing! I had to make a few small changes to get this working for my alert rules - probably due to the alert system changes with the recent versions of Orion. Here is the code I'm using: ${SQL: SELECT h.HostName FROM dbo.VIM_VirtualMachines v INNER JOIN dbo.VIM_Hosts h on v.HostID = h.HostID…

Thank you Jan! Passing the Credential solved the powershell SAM template issue that I've been working on for the past 12 hours. Thank you for sharing!

My web team would LOOOOVE AppInsight for Microsoft IIS....

Thanks aLTeReGo‌ I appreciate it. To answer your question about the user account: My access to Orion is a bit unique. My corporate Windows domain account is a member of several AD groups that are also Windows Groups in Orion user management. Because of this I needed to manually add my individual Windows user\domain account…

Thanks for the reply aLTeReGo‌. Your answer is definitely what I was looking for. Thank you. So PNRP is specific to IPv6 networks.... very interesting. I think that explains some of the other issues we are having with these nodes. The good news is that we are exclusively monitoring the workstations with the Polling Agent…

T‌hanks ecklerwr1‌. Yes I would expect the upgrade to resolve the issue too. Not sure why the upgrade didn't work for our instance but at least the KB documentation helped us. We are fully updated at well --- Orion Platform 2015.1.2, SAM 6.2.1, DPA 9.2.0, QoE 2.0, NPM 11.5.2, IVIM 2.1.0

Thank you aLTeReGo‌ for replying. I can confirm that your answer is correct. When launching performance monitor on the node we are seeing these log entries, an error displays immediately: The Windows performance counters are missing on the nodes we are experiencing issues with. This is definitely a big problem for us.…

This is what fixed the polling issue on my end. Rebuilding the counters resolved it. Thanks for this tip!

Thanks RichardLetts​ for sharing! Yes, for solely disabling all email actions during a poller reboot/upgrade, disabling all alert actions is a good option. There might be some alert actions that should be disabled, depending on the environment, but yes this is one option that would work well. The downside here is if there…

@rjg5050, thanks for your recommendation! I agree that this is one of the possible options and we might adopt this strategy during our own upgrades regardless of the negatives. When un-managing a node, you choose a start and end date & time and Orion will 'stop' monitoring it temporarily. Un-managing a node postpones…

This is answered here: https://thwack.solarwinds.com/t5/THWACK-Community-Discussions/SolarWinds-Databse-Cortex-Document-Table/m-p/251717/highlight/false#M7178