adam.beedell · SRE/Machine Learning Student · ✭✭✭✭✭

If you run it as a scheduled task you can ignore that bit. In your original post you were referring to a template, which I took to mean "a SAM Component", in which case those require some specific formatting in order to be valid. This kinda exists in the scheduled task world too, where you'd want to figure out some…

Great troubleshooting! I bet that was a nightmare

I'd recommend either search basic auth (https://swagger.io/docs/specification/authentication/basic-authentication/) or generate it from a postman or scripting tool or something. It's encrypted creds so cant really give you an answer straight up

"Basic auth" with username/pass

Worth mentioning - Pogue's talking about running this as a SAM component, in which case bear in mind the SWIS powershell module probably wont/shouldnt be on all your servers, so either you have the component in local execution mode to run on your polling engine and just install it there, or you build the API call this…

The modern ones are probably harder than classic for this for the moment You can filter a modern dashboard based on stuff in the URL, so there's a few paths possibly open 1) Table widget with sites -> Link attached to each with a generated URL filter 2) Table widget with sites -> Link attached to each to like the…

Two routes that come to mind: 1) in the Component, output the value to Statistic/Message. Then make an alert (perhaps a once-a-day), that when triggered takes the action "Write to a custom property" and write Statistic/message to it 2) In the Component, output to SWIS using the solarwinds api and calling ${caption} or…

Eu traduzi sua mensagem no Google, claramente há alguns erros, espero que seja possível. Integrar qualquer um desses sistemas deve estar ok. Você mesmo terá que criar as chamadas de API para a maioria das ferramentas que mencionou. Não vejo um problema imediato em enviar uma chamada de API que se pareça com um webhook em…

There's definitely other threads on this with more info. There's an out-of-the-box monitor for windows tasks, it only cares about the top level folder, and will only trigger based on if the task gives a sign it failed. Which is down to the author and very much not universal. There's some powershell equivalents for…

Preview number = stuff that will go off Scope number = stuff that it could go off on

I dont have teamviewer in my env, but had a client ask for something simmilar - Do you have the ability to create the link that would take you to that option? If it's a configured URL or API call it's possible

Do you mean like; SELECT RowID FROM Orion.NPM.CustomPollerStatus SELECT Status FROM Orion.NPM.CustomPollerStatus ? Or text like x.x.x.x appears in Status (not sure how that'd happen) you could separate using the verbs CharIndex, SubString and Replace to select status twice, and on one drop at the pipe, and on the other…

Aah interesting. Just checking again, but the WHERE is definitely resolving correctly too? Looks like a macro/variable/etc but not sure if it's resolving with singlequotes around it, which it'll probably need

You havnt got a FROM in the python unless i'm missing something. Possible copypasta issue?

What are you trying to show/wanting to edit? Looks like editing that page is a no, but editing the url produces different content so maybe that'll do probably you'd rebuild the table on a dash if that's the relevant bit. the selector would be hard.

Should be doable with the custom table widget or simmilar, with a query using the status in the history table for components. Maybe like [pseudocode]: select top 1 timestamp from orion.apm.chartevidence where status like notrunning and timestamp > addday(-30, getutcdate()) order by timestamp desc Hopefully that gets you…

Heard from solarwinds staffers they're trying to not use the hotfix nomenclature after a recent decision, but it's just the same thing in smaller releases, so if you ask for a hotfix and get a year.number.number answer it's that anyway.

I read this line in as "possible fix" 1315625, 1336784, 1337676, 1358723, 1359224, 1362623, 1372298 The issue where JobEngine was unable to submit a job which resulted in polling issues was addressed.

/apps/settings/node-child-status-participation or on the main settings page

You'll get a problem polling the vsphere that puts you over, you can shuffle them a bit if you've got loads of vspheres. Trying to remember exactly what stops, but it's more toward the "it stops" end rather than the "it's inconvenient" end.

Checked the status calculation page? Anyone accidentally set anything weird there?

Hi Rachel, Taking a quick look again in downtime (@"cheryl1" it takes an age to populate the variables list, i'm sure there's something poorly optimized happening there) These should work OOTB, but doesnt look like they do to me.: ${N=SwisEntity;M=DataCenter.VCenter.Name} ${N=SwisEntity;M=DataCenter.VCenter.Description}…

@"marcrobinson" Looks good! So nice when you throw something out at the end of a shift, come back and it's sorted @"Rachel.Davidson" Marc's got the right datapoint below, displayname rather than name For production purposes i'd reccomend changing the where condition to stick an ID macro in, but then it's pretty much done…

at the moment this would be something like@ 1) 30x values to monitor within the api call (and bear in mind, if someone slots in something with 5 more sensors they wont be picked up) or 2) add a filter to the endpoint if supported like x/api/temps?value={-gt{30}} And report on that as "stuff over the warning threshold" 3)…

Good point!

Appinsight templates -> no Everything else -> yes

@"Rachel.Davidson" looking at what i guess might be the table that works on there's a structure like this Hardware alarms would be on the host, so i'd try something like tas.Host.Cluster.DataCenter.VCenter.Name FROM Cortex.Orion.Virtualization.TriggeredAlarmState tas

Hi Rachel, Came to this thread thinking "I know this", and then saw that alert condition and thought "when did that go in?!" in general the macros section kinda work by calling a value with reference to whatever table your alert condition starts on (home). So if someone's alert starts in the hardware table, their solution…

Either assign a new api poller to a node and build that equivalent to postman, or you can use a https monitor component in an application template for some basic stuff, or you can do the same in a script monitor component for advanced stuff. (Script components should exit in a solarwinds format described in other threads)

I havnt got HCO proper in my environment, but I see the above as "SAM" which is not wrong as I understand it. I've just got myself some SWO which is the cloud-native tool, and that's cloud monitoring is markedly more straightforward. Had heard the goal was for some level of feature parity across the on-prem/cloud/hybrid…