This is a post about using Microsoft monitoring tooling to monitor a device with an API. It will be a series of posts, due to different things to take care of and different ways to monitor and display data. I will be using part of my home automation for this, which is a Philips Hue Bridge and some smart lights and sensors. This is not a sponsored post (although I will accept any help). And this is about giving an example of monitoring an API based device with Microsoft monitoring tooling. You might have different devices or apps with API’s that you may want to talk to, but you can still use these methods and adjust them accordingly.
First of all I will explain how to get access to the device and to start talking to it using PowerShell. Next as first monitoring product I will use SCOM to try and discover the device and next to discover its components. After that we get into collecting data and monitoring. The next step is display/dashboarding. After that we will be trying Azure Monitor for data collection and find ways to display the data from that platform.
Table of contents:
- Main page with Table of contents
- Introduction and device setup
- Getting access to Philips Hue Bridge
- Starting a SCOM pack with Classes
- SCOM Setting up Discoveries
- SCOM Collecting data and performance view
- SCOM Monitoring, state views and tasks
- Azure Monitor
There may be more chapters, but this is a starter 🙂 And give me a bit of time creating the content in this list.
- Aside from the monitored objects which I will cover in the next chapter…
- Microsoft SCOM 2019 as the first monitoring tool to explore the connection with.
- Notepad++ to create the basis of the management pack.
- Visual Studio Code to play around with the PowerShell scripts.
- Silect MP Studio to continue the management pack testing and version control.
I guess it is time to get started.