New release for #Azure #SCOM MP addendum


Today I just released version 1807 of my SCOM Azure Management Pack addendum. You can find the new release on github.

In this release I added:

  • support for Azure Monitor so that any enabled alert rule is discovered in SCOM, plus any New and unresolved alert is signaled in SCOM (and resoleved when it’s not new or unresolved anymore)
  • support for Azure Backup for SQL Databases in virtual machines

Alert rules can be checked under the folder QND – Azure\Azure Monitor\Alert Rules

alertrules.png

the point of having Azure Monitor alert in SCOM is all about getting a single console to manage alerts and notifications. While I’m sure in the future we will start to do exactly the opposite (i.e. sending SCOM alert into Azure Monitor), today this is premature.

For Azure Backup I just added support for the new SQL Database running inside a VM workload. Recently all the Azure backup logs have been integrated in Log Analytics, so now you have two options to monitor Azure Backup protection, either you use the SCOM MP or you integrate Azure backup with Log Analytics, define your alert rules in Azure Monitor and get the alerts back into SCOM that way.

dbmonitor.png

As usual any contribution is welcomed, especially for documentation and KB articles.

Advertisements

,

  1. #1 by Stephen Morrison on July 25, 2018 - 11:09 pm

    I have an indirect question, With the MS Azure ARM MP Alert Rules showed up as monitored objects in the service state view. But I am now seeing objects labeled as ActivityLogAlerts that don’t have a health state.

    I am not sure if this is due to the newest version of the MP or the new alerts(preview) that they are building in Azure as they migrate from the OMS workspace.

    • #2 by Daniele Grandini on July 26, 2018 - 7:43 am

      Hi Stephen, you’re right the MP discovers all enabled alert rules migrated from LA to Azure Monitor, infact the previous discovery for rules in LA has been disabled in this new release (you can turn it on if you want to). So you should see all the alert rules monitored (i.e. green or red) in the status view.

      • #3 by Stephen Morrison on July 27, 2018 - 4:09 pm

        This management pack is meant to be a compliment of the Microsoft.Azure MP or a replacement? I have both installed. I didn’t find any instructions with yours so I am not sure if I have to populate any data for the discoveries to work. Under Azure Monitor -> Monitor accounts I see it did discover my subscription name and ID but has since turned critical. no other views have populated. Within the event viewer the discovery events are informational but there are many cannot get storage account key **** events.

        Also
        Main Exception processing query System.Management.Automation.ErrorRecord The ‘Content-Type’ header must be modified using the appropriate property or method.
        Parameter name: name Exception processing query System.Management.Automation.ErrorRecord The ‘Content-Type’ header must be modified using the appropriate property or method.
        Parameter name: name Exception processing query System.Management.Automation.ErrorRecord The ‘Content-Type’ header must be modified using the appropriate property or method.
        Parameter name: name
        Version :1.0

        I don’t believe we have any automation workfloads in Azure yet so maybe I just have to remove that MP.

      • #4 by Daniele Grandini on July 30, 2018 - 7:20 am

        Hi Stephen, the MP is an addendum to the Microsoft one. All the monitored resources are automatically discovered once you’ve registered the subscriptions in the Admin pane. If Azure Monitor doesn’t have any alert rule defined it will turn red, this is the expected behavior. You can create a couple of dummy rules to fix it, actually there’s a bug I’m going to fix which requires at least 2 rules, in the near future I will release fix that requires just one rule to make things working. The error you’re getting is new to me, the reference to Automation is not to Azure Automation but to the Azure REST API.

      • #5 by Stephen Morrison on July 31, 2018 - 8:10 pm

        We have the Microsoft Azure (v1.5.20.18) installed. We have many classic and new alerts setup in the subscription. I have enabled trace level logging in an attempt to see whats going on,

        [QND.Get-GenericAzureResource] Main got error: Exception calling “ReturnItems” with “0” argument(s): “The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))” for
        Version :1.0

        [GetAzureMonitorSummary] Main got error: Cannot index into a null array. for
        Version :1.0

      • #6 by Daniele Grandini on August 3, 2018 - 4:20 pm

        At what level did you set the trace level, the maximum you can use is 4, 5 is just for testing scripts outside OpsMgr. This should explain the ReturnItems error. The GetAzureMonitorSummary is something different I’m not experiencing in my production environmentsmonitor uses the GetSummary.ps1 script which in turn calls the Microsoft.AlertsManagement/alertsSummary REST API, it is a very simple script the only thing I can think of is the REST API returns nothing for your subscription…

  2. #7 by jaspervd86 on July 13, 2018 - 9:15 am

    Hey Daniele, great work once again. I was planning on building something similar but couldn’t find the time to, thanks for putting in the effort and I’ll definitely check this one out.

    • #8 by Daniele Grandini on July 20, 2018 - 4:00 pm

      Hi Jasper, let me know if you find any bug.

    • #9 by Daniele Grandini on August 7, 2018 - 4:17 pm

      Just a question have you activated the new alert experience currently in preview? this is needed for proper Azure monitor integration.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: