fop · 3rd Level Techromancer · ✭✭✭✭✭

The thing that tripped me up back in the beginning was that for OAUTH2 you need the tenant (directory) ID to get an access token. It also requires which backend process you're using for the data, eg a plain Microsoft login for a service endpoint or a Microsoft Graph. 90% of ours are plain logins against the endpoint we…

This is quite a vague question because we don't know what setups you have for authorisation in the API call, or what you're looking at monitoring. I use APIs for Azure polling and this might be different to what your aim is. I'll say one thing though, the biggest pain and the most poorly documented is OAUTH2 authorisation…

What's the end point here? Are these new servers that you need to onboard for monitoring?

Ah, this is the Macros I've been learning about this week. They're context based and I haven't worked out how the context works yet, but I assume it's a subset of the query in the dashboard SWQL. Your usage of [dbo] there makes me think you're doing a SQL query and not a SWQL one? Or just listing the field names in the…

Your SWQL query is wrong since you won't have a table called OSG_Company in the database. If you post the code we'll be able to track the problem down.

So you want the alert to fire at say, 1pm, but you want that alert to immediately go away and not fire again until 1pm the next day even if the trigger condition matches?

In the alert definition, go to the 'reset condition' tab and select 'reset this alert automatically after', then give it the number of hours needed, probably 23 in your case. This will keep the alert active and won't retrigger until that time period has expired.

I can see the top line in that script that says 'Arguments example', so is the script in your component monitor expecting the arguments and starts with $logfile_path = $args[0] $regex = $args[1] instead of what you're showing us from the ISE where those variables are populated manually? Can you send a screenshot of the…

No problem :) 

Go to customersupport.solarwinds.com and log in, then go to this menu: The Environment Reviews page explains the process, but handily gives the wrong location for the Diagnostics collection tool, on my Poller(s) it's in Start -> Solarwinds Platform -> Solarwinds Diagnostics. Run that and click 'start and save diagnostics'…

Two things you can do to give you an instant (ish) overview of your SW estate: 1) Download the 'SolarWinds Platform License/Polling Usage Summary' report from here. It gives you all the info SteveK mentions but laid out in a much easier to understand manner, to me anyway. 2) Create a diagnostic bundle on your poller(s) and…

Since you have a support contract I'd create a diagnostic bundle on all pollers including the original 2016 ones, then upload them to the customer portal - Orion Insights | SolarWinds Customer Portal After a few hours you'll be able to download a report for each poller which breaks down the resource usage etc, and will…

I'm really going to have to change my name. I only registered quickly while a colleague was on holiday - this was for App Gateway API stuff. I was going to scarper when he came back, but enjoyed having my programming head back on so much I decided to get stuck in

Hi Robert, I have Veeam monitors running for failed jobs etc. The powershell script that queries output of the Get-VBRJob cmdlet is in the application as 'Job status 1' and returns the job name and result in this format: Message.Job_Name: Daily VM Backup New[0] Statistic.Job_Name: 0 (0 is success in this instance) In the…

Absolutely, and as someone said in another thread, if you're trying to pull credentials out of something to use for authentication WITHOUT authenticating yourself first you're still leaving a massive security hole.

I suppose it's not an absolute showstopper since I can do it in SAM as you say, but I do wonder why SW thought it 'might be handy' if the date was converted to a more human friendly string with no way of converting it back. Our test env is running 2024.1 so I'll try it there just in case the devs came to their senses in…

I remember you mentioning this the other week and you said it was something you were looking at, so I def need to pursue it since it would be nice to publish it in the content exchange.

It can, and I've written a SAM Application to do it which works well on our pollers. But, it's far from secure which is why I haven't published it. The big issue is around the necessary Oauth2.0 authorisation which requires an ID and secret to be passed. Currently I'm doing it in clear text which is far from ideal. So far…

So it IS that certificate? That's bonkers, utterly bonkers. SWQL Studio is supposed to be a tool you can give to non-admins if the need arises. I've already got it working by doing that but thought that CAN'T be the only secure way of doing things and there must be a way of generating your own cert. My users can't have it…

I'd never heard of the swagger until I saw you mention it the other week, I still need to dig into it to see if we could use it effectively. For the creds, I suppose it's one of those issues that no matter how you approach it you add another layer of insecurity The other issue is as I've just posted here about SWQL Studio…

I'd forgotten about this. I did get it running successfully and had it alerting when a backend server went down. However, I didn't deploy it because I was using the client ID/secret in the script and didn't like that lack of security. I reasoned that there must be a way of pulling the Oauth2 credentials out of SWIS and…

Hi popem, The Priority column in the resulting config is the priority of poller connections, so if you use connectionSetId to 0 for all new installs then the higher priority takes precedence, at least in my testing. I've used a connectionSetID of 1 as well, to populate the config of already established agents. This was…

OK, a fix When an agent is provisioned, the poller it's connected to will send up a system-generated config to overwrite whatever you put in the MST file. I don't believe you can stop this happening. What you CAN do is add entries to the AgentManagement_PredefinedConnectionSets table which are added to the system generated…

OK, Modern Dashboards are no good in this scenario. By design, a modern dashboard owner has automatic edit rights to their dashboard even if 'manage dashboards' is turned off. This doesn't affect Classic Dashboards which is way we've now gone for this particular scenario. Personally I think that's an oversight and setting…

Sort of success. The page visibility and owner is key, I realised all our modern dashboards were set to be public, so I changed the visibility to be private and the dashboard to be owned by the user account only. This gets rid of using URLs to view other pages because they're now not accessible and return 404s. Excellent.…

Hi Steve, Strangely, today I can't access Manage Nodes from that account whereas 2 days ago I could. We have 2 AWS' though so I wonder if I was just too quick to test after making the changes, and the account restriction hadn't made it to one of the others - this has happened a LOT in the past but I thought we'd fixed that…

Hah! Turns out that the node that 'works' doesn't, or didn't. Agent was running and I got the correct response when I went into the Agent GUI, but the logfile showed me it wasn't connecting to the poller, and that turned out to be because the Azure NSG for that particular server didn't allow port 17778 outbound. Slightly…

Found it. The agent initially connects with the info in the MST and finds the poller correctly. Then for some reason this happens: 24/02/15 15:23:41.258 PID: 10780 TID: 11076 [INFO] AsyncTaskManager::OnClientConnect - Server with device ID [6C8E0057-F2C4-410F-9812-CC80D00B4A23.AMSF] was connected 24/02/15 15:23:41.258 PID:…

Thought I'd add the relevant parts of the two config files in question once I'd sanitised them. This is from the working node. and this is from the non-working node: It's baffling. 

Yep, I can see that by dumping the MST. What I can't see is where the SolarWinds.Agent.Service.exe.cfg comes from. On the working node it's a simple file with a single entry for the FQDN and IP address I configured at MST creation. On the non-working node (installed from the same files remember) it's a monster config with…