Anyone tried to use "Component Monitor Wizard" to monitor Azure Application Gateway before?

What are you trying to monitor about that gateway?
I'm doing some Azure monitoring currently, everything's doable but i've found azure stuff pretty hard

Hi there - I try to monitor the https status, throughput or total request something like that just below.

But I am really scratching my head where to start on.  I even wonder if we can send over the application gateway logs to solarwinds SAM.

and YES - this is quite hard to configure it as it's lack of documentation ( or I don't know how to search them well in here..)

On a whim I created a SAM powershell template assigned to a dummy node that just does this:

[int]$foo=$PSVersionTable.PSVersion.major
Write-Host "Message.Health: Health: Version";
Write-Host "Statistic.Health: $foo";

On my poller it returns V5 so that's what it's using to execute scripts. I've got PS7 installed but haven't enabled it as default. That will fix this issue I think.

Interesting! I must've been going off way outdated knowledge there

...and the bad news is I've just had official clarification from Solarwinds that SAM uses 5.1 only and changing to v7 isn't even on their roadmap for future development so I've requested it as a feature.

This doesn't help me right now of course. The invoke-restmethod parameters my script needs only came in in v6 so I need to see if it's possible to get the response headers out of the 5.1 version of that cmdlet. Trouble is, MS's own docs vary from awful to terrible on this sort of subject.

A

fop Please add the link to this feature request, so we can all bump it up. Calling the bumpsquad! As to your pain with Microsoft and Azure - umm you are not alone. I get very similar reactions when I talk to the Azure Architects. This is often mentioned with a comment to wait two weeks, Microsoft will update Azure to invalidate what you just did . Creating and provisioning an MS Graph application solves many, many api issues by design. The App Gateway Team didn't get that memo from what I can tell. They wanted their own twist in authentication. This thread seems to validate the pain from my thread on this topic too. 

Microsoft Azure Application Gateway API - Forum - The Orion Platform - THWACK (solarwinds.com)

You're trying to use the -ignorecertificateaction thing right?

Hahaha, it's so good to see I'm not alone 

My Solarwinds tech said 'I will open a feature request for you and send it to the Development team, as the requested functionality is currently not part of our product line. ' but he also linked to the Feature Request here so I'll do that too.

As it happens, I was THIS CLOSE to sorting it on v5 last week and hadn't realised, so a couple of command changes later and the script runs on v5 and returns the correct results.

In Orion of course, it fails with this spectacular error - "The response content cannot be parsed because the Internet Explorer engine is not available". I just needed to add -UseBasicParsing to get around that one.

(+) Orion SAM to be upgraded to use Powershell V7 - Community Feature Requests - THWACK Command Center - THWACK (solarwinds.com)

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 implementing them that way, but I was still new to SWQL Studio back then. 

These days I've a lot more knowledge under my belt so it's worth another stab at it I think. There's still the issue of connecting to SWIS first though, but I think I'll cover that in another forum post.

There's an easy command for connecting to SWIS in the powershell module, without the powershell module you'd be using the swagger, which is also fairly easy to work with

For the creds problem you get one for free as whatever cred you assign against the component. You could use that cred to encrypt/decrypt another set.

I've got a decent idea for salt+pepper+hashed passwords but havnt implimented it yet

Never saw this reply at the time, but FYI stuff like the -usebasicparsing thing is like profile-based issues, there's a bunch of those, and there's a class of fix which is basically

1) Confirm the account you'll be using for the script, dont change it without redoing later steps
2) On the account you're using above, do the things to prepare the profile (Open IE, install a module, etc)
3) if need be, add them as the result of a CATCH block

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 and SWIS connections in general.

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 and SWIS connections in general.