dnerdahl

See, now... that makes complete sense. Unfortunately I'm usually comparing MINUTE() to a two character format because datetime fields store minutes in a "01,02,03,04" format.

SLA and Availability reports for IT services is a great place to draw attention to that pesky objects in error that may have an inconceivable impact. Allowing you to filter them out a view within the Solarwinds tool and still be reporting accurately and honestly about it's state.

jrouviere​ Ultimately you want to fix everything. All the things. I know I do. Unfortunately, sometimes the technology owner of the object in a state of error simply isn't motivated to fix it... but that's a whole other conversation. You make really important points about scope. I want all the data. I mean, don't we all?…

That was exactly it. The DCOM permissions were not correct. Thank you for your response!

I'm going to wait for a further response from rtobyr at this point. I reread his post and I'm no longer sure what his objective or problem is. By the sounds of it I would say HolyGuacamole has hit the nail on the head. I would image that your alert is, infact triggering at 2:30am however, your trigger action is restrained…

Thank you bluefunelemental I didn't think I'd need to ToString() the ObjectName since it's a text field... but that did the trick.

In our installations of Windows 2k8r2 they were located in c:\ProgramData\Solarwinds\Discovery Engine

I second the Success Center. There's so much good information in there. Also take a look at the up coming events. The Solarwinds Academy events are great for getting off the starting line.

Your problem is with the last part of your statement: Vendor = 'GTE' AND Status<>2 AND Node.LastBoot There is no comparative syntax following 'Node.LastBoot '. If You remove the syntax in red above, or finish the comparative statement, it should filter correctly. Please note, you can not add a column of data to a…

I'm with adatole‌ on this. Particularly the use of Groups/Containers. They have an extremely robust dynamic query engine that accepts regex. That way as new "XA" servers come onto or off of the network they are automatically added and removed from your group and from the scope of your group member alert. There's a reason I…

I'm on NPM 9.1 - SP3 There is no limitation defined for the user, only the view. Thanks!

Craig Norborg has great points to consider here. Specifically the "Node Warning Level"and "Default Node Polling Interval" settings. For the issue with the status updating, those settings are likely your culprits. I would however like to add that you should check these tricksters located on the Trigger and Reset tabs of…

billyjbryant I just completed a support case on this issue. Unfortunately this behavior appears to be working as intended. Specifically this is linked to the "Owner" field. Even with Admin privileges reports and limitations are filtered by owner outside of the limitation that you are assigned to. Support suggested that a…

tdanner​ Thank you for the reply! * This makes me extremely excited. The shear volume of queries I'll be able to convert from SQL to SWQL would keep me busy for weeks. The reliability of queries written to the SDK schema vs. directly to the database tables makes my business continuity personality very happy. I've been…

BUG FIX - an error in the trigger coding has been corrected that prevented the first of two time spans entered into "z_n_exception". The alerts were only evaluating the second of the two time spans.

thawkson , Thank your for the comment. I had not realized I had completely left out the reset queries from the document. A new version has been uploaded with the reset queries included.

pschellhaas I am aware of the issue with the automatically created reset queries created by the alert manager. It's important for people to be aware of this issue. We discovered this the hard way. The reset queries that are contained in the document have been hand coded and tested to work. We have been running them in…

... and fixed a bug caused by the bug fix...

BUG FIX - an error in the trigger coding has been corrected that prevented the first of two time spans entered into "z_n_exception". The alerts were only evaluating the second of the two time spans.

It is just a copy/paste operation into a text file and saving it as a .vbs

Well, we'll just call that an undocumented feature... and then remove it... like I just did... Thanks for the heads up xtraspecialj​

Database scheme has changed. This query does not properly exclude components that are assigned but disabled.

After some work, my team got Gob's resource working in our environment. We uploaded the fixed files for download. I know it's been a year, but we were looking for the same thing a year later. All triggered Alerts.Filtered fixed

I'd like to agree with Mike on the color issue in the graphs. I've had a number of questions since upgrading to 10.5 as to why there are random gold/yellow bars on a graph where that color is not in the legend. I see not having consistent colors on a graph as an issue and not a feature request.

If your speaking to removing a custom property from the custom properties resource in the web console you can hide custom properties by using "edit" for the resource (not the custom properties) with in the view. Then you can select which properties are viewable in the resource. As a side note, properties that are not…

This all depends on the type of component monitor that you're attempting to obtain the data for. If you're looking for CPU or Memory data from a process or services monitor, they are stored in Orion.APM.HistoricalCPULoad and Orion.APM.HistoricalMemory respectively. If you're looking for historical statistical data for…

I posted about this same issue early this year (). They keep saying they're going to fix this in an up coming release. I don't know when the release is scheduled to happen, but it's very possible that my boss is going to want to toss it out the window if graphing for custom time periods isn't working soon.

There are several key metrics to understanding the load on your pollers. Elements - is the total number of NPM related elements being polled by the poller Network Node Elements - is the total number of 'nodes' being polled by the poller. Volume Elements - is the total number of 'volumes' being polled by the poller.…

After restarting the services I just let the server settle in. It took about 45 minutes however, the three transactions in question returned to working order. ... although... it would nice to know why it was displaying that behavior.

There are a few approaches that might work for you depending on the type of alert that you've configured. I would start by suggesting the ${GroupStatusRootCause} variable. This variable contains a coma separated list of all the group members that are contributing to the group's current status. Which can then be added to an…