mesverrum · Observability Architect · ✭✭✭✭✭

To my eyes it seems to be working, assuming you still get an exit 0 with a statistic when the stat is good then I would feel reasonable comfortable ignoring that. It would mean that your 0-1 chart won't show up anymore the way it did, but thats just a design limitation that when solarwinds gets an exit code 1 it won't even…

Rahmat, The script you are running is not meant to be fed directly into a switch, it may "complete" but it definitely won't achieve the desired results unless you run it through the correct tool. You need to go to Configs > Config Change Templates and import it into that section. Once it is imported you can run the change…

You should be using the resource called "Custom Query" for the code I pasted in. I just mentioned the custom HTML as the example for if you need to do something that somehow can't be accomplished with the Custom Query or Custom Chart widgets. This thread is probably one of the oldest I know if where the _linkfor and…

its written for the custom query resource, won't work correctly in any other resource. You'll never see me post anything for legacy report writer haha, I constantly discourage people from using it.

I also find that the most accurate uptime reporting is event driven like this as well. That way the numbers dont get skewed by unmanaged objects and I have lots of control over things like scheduled/ unscheduled downtime

Yeah, to rule out possibilities. If I can't run that then I know I'm not even getting connected to the server properly

This was written to use in the custom query resource, custom table is a little fussy about some of the more advanced swql maneuvers.

Gets something like this Also created this table in SWQL with a custom query widget, if you want to get realllllly technical the peak it tracks is a bit of an estimation but the people reading the chart aren't worried about the specific detail on a given day as much as they need to know the general numbers. select top 7…

Then it would sound like you go to as high of a version as is compatible within your accreditation and do not upgrade beyond that until the next accreditation cycle. With a locked down environment like that I imagine that not running the latest and greatest of all software is somewhat expected. 

I've seen in the past where different versions of Orion had bugs that would result in bogus event entries. You may be encountering one such case here, support ticket is definitely the way to proceed.

Its just called the component called http form login monitor

So right now you don't have anything to connect the two sets, you need to have something that overlaps between them, according to what I see in the mib 1.0.8802.1.1.2.1.4.1.1.2 should be workable but my test HP devices didn't respond to that oid so I'm not sure if HP didn't implement it or if I just have trash in my lab.

Yes, one of the built in SAM component monitor types you can create is o watch the results of custom powershell scripts, the last 3 links there outlines how that is all set up and the kinds of outputs it expects to get back. -Marc Netterfield Loop1 Systems: SolarWinds Training and Professional Services * LinkedIN: Loop1…

I would just make a copy of the out of the box hardware sensor alert and use that as my starting point. If any sensor is critical notify the owner of that node. Getting under the covers and building your own duplicate snmp poller for the same stats that you know you are already polling is redundant and pointless. No swql…

You probably also want to do this, to deal with cases where there is nothing in that property. be default if you query returns a null then Orion displays the whole query which makes alerts pretty ugly. ${SQL: SELECT isnull(Email,'None') FROM AlertConfigurationsCustomProperties WHERE AlertID = '${N=Alerting;M=AlertID}'}

Yep, save anything you build in perfstack and then it will be added to the list of available resources/widgets on the view editing screens.

yep you got it

You need to put the entire query into that second box, its really running two completely separate things. I sometimes write custom queries with high level info on the initial screen and then if you search any of the values it gives you a different, more detailed set of data based on the search filter.

The ones that show up as "1 value" are table pollers, in this case they only have one item on the table though so converting them would probably be fine on this node, can't say for sure that would apply to other nodes.

ah yes, good looking out, i'll edit those lines on the post as well

This is a screenshot of the built in alert example for hardware sensors, you can look for it in your environment and copy it and use it as a model or come up with your own.

probably something along the lines of adding a "where [minutes] > 60" near the bottom, but i feel like it may be a bit more complicated than that -Marc Netterfield Loop1 Systems: SolarWinds Training and Professional Services * LinkedIN: Loop1 Systems * Facebook: Loop1 Systems * Twitter: @Loop1Systems

Pretty strange, you can go to the sql and confirm the actions taken with each alert in the orion.alerthistory table. If it runs into an error sending an email there is usually some indication of it in the "message" column. Beyond that I would be looking toward your mail server. Does it have any kind of rate limiting if it…

That's because your retention settings do not hold detailed stats that long, the default is only 7 days of granular data. You have to increase your default retention to at least 30 days run the report for the current month.

alexslv​ Agreed, i feel like the existing groups functionality is pretty much a trap that most new Solarwinds admins fall into, spend a ton of time working on and then either realize the limitations of it and ditch them for custom properties, or they don't want to lost the effort they put in so they keep at it regardless.…

solarwinds only shows nodes in warning when they are responding intermittently to the ping requests from the poller. If all settings are at default then they should have gone down after 120 seconds of continuous missed pings.

This query is written to be used on the web console, those tables definitely do still exist in SWQL, I've been using it in several environments for nearly 2 years. Not sure why you can't access it, but try adding the query to the web console and see what you get.

The _linkfor_ syntax only works if you use the query inside a resource they call a "Custom Query", you can add that resource to views or to reports but it doesn't show up on the initial screen of resources for reports, you have to search for it. As far as the additional columns, whenever you write a report using custom…

I am still pretty confident it is your AD Site, on one of the systems where you do have it run this and see if it gives you back the same value as what you have in your Location field nltest /server:<computername> /dsgetsite As far as machines where it isn't populating, I checked my current client and they had about a…

You'd also need to add to your trigger condition that the status is down, when the status is up then there's no event to match to