Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Azure API monitoring

marklbuk

I am trying to follow the guide to setup monitoring, but draw a blank when it comes to this line.

Go into the Node details page of the node you would like to assign this API poller to

If i want to monitor a Storage Account or Gateway there will be no node to associate to, what does everyone else do ?

Thanks

Mark

Find more posts tagged with

Accepted answers

All comments

adam.beedell

There's a guide or two on here but I found them totally incomprehensible personally.

You can make some random External node or two and assign to that, or assign to your polling engine, doesnt matter really.

Permissions can be a faff, as can expiring secrets

Personally my biggest bugbear has been the "scope" header as part of the login process and trying to set that correctly.

If you've got data that's going to change shape frequently you probably want to build an integration with a script of some sort.

marklbuk

Thanks Adam, I will have a look and let you know

marklbuk

Hi Adam, can you supply any help or hints with the headers, I am getting authorisation header is missing .

Any help appreciated

Mark

marcrobinson

Storage account sounds interesting. The gateway is another ugly thing entirely. I have noticed that the app gateways want the token refreshed hourly, and the api monitor does not seem to have this capability currently.

Let me poke around a bit and try to find some other posts to cross reference about Microsoft. The changing nature of azure and the fact that different parts vary in how you access them via api is less than helpful.

Adams comment about creating an external node is spot on. This allows you to also create some organization with these api calls. I would recommend using the fqdn for the specific site that you are calling.

For Microsoft these would include graph.microsoft.com -> this would usually be the starting url for any call against a graph application. management.azure.com is another common endpoint.

Lastly - get Postman. Its free to use and is great to test api calls and validate what is or is not happening when setting up an api monitor. https:www.postman.com. Many vendors publish api collections to it that can be downloaded and tested.

Can you throw a link to the which microsoft api that you are trying to use? Specifically the support/tech doc for the storage resource.

adam.beedell

They're different based on the metric and the environment so this is hard to advise on. (also just hard, i've got a few working in live and have struggled)

Chatgpt is excellent at sorting out azure headers