%3CLINGO-SUB%20id%3D%22lingo-sub-1271326%22%20slang%3D%22en-US%22%3EChanges%20in%20Alert%20Management%20of%20SCOM%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271326%22%20slang%3D%22en-US%22%3E%3CP%3EUsage%20of%20SCOM2019%20has%20been%20surging%20since%20its%20inception%20and%20we%20really%20appreciate%20all%20the%20feedback%20that%20we%20have%20been%20getting.%20As%20the%20product%20evolves%20to%20accommodate%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsystem-center-blog%2Fscom-2019-ur1-a-must-read%2Fba-p%2F1164417%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Enew%20features%3C%2FA%3E%2C%20there%20were%20few%20issues%20which%20needed%20immediate%20attention%20and%20we%20have%20released%20a%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4551468%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EHotfix%3C%2FA%3E%26nbsp%3Bto%20fix%20them.%20Well%2C%20what%20are%20those%20issues%3F%20Read%20on..%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1116678133%22%20id%3D%22toc-hId-1116678133%22%3E%3CSTRONG%3EAbility%20to%20edit%20Alert%20Property%20Columns%20irrespective%20of%20Health%20State%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%0A%3CP%3EWhen%20a%20new%20Alert%20is%20raised%20by%20a%20Unit%20Monitor%2C%20the%20existing%20Closed%20Alerts%20created%20by%20the%20same%20Unit%20Monitor%20could%20not%20be%20updated.%20This%20functionality%20blocked%20changes%20to%20Alert%20properties%20such%20as%20Custom%20fields%20TicketId%2C%20Owner%2C%20Custom%20Fields%20or%20Alert%20History.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23FF0000%22%3EFix%3C%2FFONT%3E%3C%2FSTRONG%3E%3A%20User%20will%20be%20able%20to%20edit%20columns%20on%20closed%20Alerts%20irrespective%20of%20Health%20State.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_0-1585744699370.png%22%20style%3D%22width%3A%20785px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181268i69952AF1CAF47B21%2Fimage-dimensions%2F785x580%3Fv%3D1.0%22%20width%3D%22785%22%20height%3D%22580%22%20title%3D%22AakashMSFT_0-1585744699370.png%22%20alt%3D%22AakashMSFT_0-1585744699370.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--690776330%22%20id%3D%22toc-hId--690776330%22%3E%3CSTRONG%3EIssue%20with%20Alert%20Closure%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%0A%3CP%3EWhen%20an%20alert%20is%20closed%20for%20the%20below%202%20scenarios%2C%20user%20would%20get%20an%20error%20%22Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%22.%20Let%20us%20look%20at%20these%20scenarios%20in%20details.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_1-1585744699373.png%22%20style%3D%22width%3A%20426px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181269i6863F2260868A02C%2Fimage-dimensions%2F426x282%3Fv%3D1.0%22%20width%3D%22426%22%20height%3D%22282%22%20title%3D%22AakashMSFT_1-1585744699373.png%22%20alt%3D%22AakashMSFT_1-1585744699373.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--214856%22%20id%3D%22toc-hId--214856%22%3EScene%201%3C%2FH4%3E%0A%3COL%3E%0A%3CLI%3EUser%20creates%20a%20monitor%20but%20%3CSTRONG%3Edisabled%3C%2FSTRONG%3E%20the%20option%20to%20%22Generate%20an%20alert%20for%20this%20monitor%22.%3C%2FLI%3E%0A%3CLI%3EUser%20sets%20an%20override%20to%20generate%20an%20alert%3C%2FLI%3E%0A%3CLI%3EAfter%20an%20alert%20is%20generated%2C%20if%20user%20tries%20to%20close%20it%20-%20oh%20oh%20..%20Error%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_2-1585744699365.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181267iC132CC990B46F2B4%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22AakashMSFT_2-1585744699365.png%22%20alt%3D%22AakashMSFT_2-1585744699365.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--1807669319%22%20id%3D%22toc-hId--1807669319%22%3EScene%202%3C%2FH4%3E%0A%3COL%3E%0A%3CLI%3EUser%20creates%20a%20monitor%20with%20(%3CSTRONG%3Eenabled%3C%2FSTRONG%3E)%20the%20option%20to%20%22Generate%20an%20alert%20for%20this%20monitor%22.%3C%2FLI%3E%0A%3CLI%3EOnce%20an%20alert%20is%20generated%2C%20User%20disables%20the%20option%20to%20%22Generate%20an%20alert%20for%20this%20monitor%22.%3C%2FLI%3E%0A%3CLI%3ENow%2C%20if%20a%20%60user%20tries%20to%20close%20the%20alert%20--%20Error%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_3-1585744699360.png%22%20style%3D%22width%3A%20458px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181270iE23CA1832B4EF1AE%2Fimage-dimensions%2F458x246%3Fv%3D1.0%22%20width%3D%22458%22%20height%3D%22246%22%20title%3D%22AakashMSFT_3-1585744699360.png%22%20alt%3D%22AakashMSFT_3-1585744699360.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3CSTRONG%3EFix%3C%2FSTRONG%3E%3C%2FFONT%3E%3A%20Alerts%20can%20now%20be%20closed%20if%20the%20underlying%20Monitor's%20Alerting%20i.e.%20%22Generate%20an%20alert%20for%20this%20monitor%22%20is%20disabled.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1818172423%22%20id%3D%22toc-hId--1818172423%22%3E%3CSTRONG%3EImproper%20message%20on%20Web%20Console%20when%20closing%20Alert%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%0A%3CP%3EWhen%20a%20user%20tries%20to%20close%20an%20Alert%20of%20an%20unhealthy%20Monitor%20from%20the%20(legacy)%20Alert%20View%2C%20a%20pop-up%20with%20random%20text%20was%20displayed.%20User%20had%20no%20idea%20what%20just%20happened.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3CSTRONG%3EFix%3C%2FSTRONG%3E%3C%2FFONT%3E%3A%20Message%20on%20Pop-up%20is%20meaningful%20now.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_4-1585744699367.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181271i262EB9BC60BF0BBB%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22AakashMSFT_4-1585744699367.png%22%20alt%3D%22AakashMSFT_4-1585744699367.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-669340410%22%20id%3D%22toc-hId-669340410%22%3E%3CSTRONG%3EAutomatic%20Alert%20Resolution%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%0A%3CP%3EOn%20the%20Operations%20Console%20of%20SCOM%202019%2C%20we%20have%20a%20feature%20which%20closes%20any%20alerts%20after%20certain%20period%20of%20time%20based%20on%20the%20settings%20and%20it%20is%20called%20Automatic%20Alert%20Resolution%20(Operations%20Console%20%26gt%3B%20Administration%20%26gt%3B%20Settings).%20Upon%20double%20clicking%20this%20feature%2C%20we%20found%20that%20Alerts%20for%20unhealthy%20monitors%20were%20closed%20even%20though%20SCOM%202019%20brought%20in%20this%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsystem-center%2Fscom%2Fmanage-alert-created-by-monitor%3Fview%3Dsc-om-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3CSTRONG%3EFix%3C%2FSTRONG%3E%3C%2FFONT%3E%3A%20We%20got%20in%20a%20couple%20of%20changes%20for%20Alert%20grooming.%3C%2FP%3E%0A%3CP%3E1.%20Segregation%20of%20Rule%20based%20alerts%20and%20monitor%20based%20alerts%20on%20Automatic%20Alert%20Resolution%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CTABLE%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20class%3D%22lia-align-center%22%3E%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3ECurrent%20Behavior%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20class%3D%22lia-align-center%22%3E%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3EAfter%20installing%20KB4551468%20Hotfix%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_5-1585744699372.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181272iB12000E227DDCEE2%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22AakashMSFT_5-1585744699372.png%22%20alt%3D%22AakashMSFT_5-1585744699372.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FTD%3E%0A%3CTD%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AakashMSFT_6-1585744699368.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181273i7442ACB57B4B8DF8%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22AakashMSFT_6-1585744699368.png%22%20alt%3D%22AakashMSFT_6-1585744699368.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20Alert%20from%20Monitors%20cannot%20be%20closed%20until%20monitor%20is%20healthy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EGot%20Feedback%20on%20SCOM%3F%20Let%20us%20know%3A%20%3CU%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FSCOMFeedback%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FSCOMFeedback%3C%2FA%3E%3C%2FU%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F464069%22%20target%3D%22_blank%22%3E%40AakashMSFT%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F196592%22%20target%3D%22_blank%22%3E%40Vithalprasad%20Gaitonde%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F291335%22%20target%3D%22_blank%22%3E%40NehaGarg%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1271326%22%20slang%3D%22en-US%22%3E%3CP%3EHotfix%20Alert%20-%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4551468%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%26nbsp%3B4551468%3C%2FA%3E%20!!%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1271326%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Escom%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESystem%20Center%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESystem%20Center%20Operations%20Manager%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Usage of SCOM2019 has been surging since its inception and we really appreciate all the feedback that we have been getting. As the product evolves to accommodate new features, there were few issues which needed immediate attention and we have released a Hotfix to fix them. Well, what are those issues? Read on..

 

Ability to edit Alert Property Columns irrespective of Health State

============================

When a new Alert is raised by a Unit Monitor, the existing Closed Alerts created by the same Unit Monitor could not be updated. This functionality blocked changes to Alert properties such as Custom fields TicketId, Owner, Custom Fields or Alert History.

 

Fix: User will be able to edit columns on closed Alerts irrespective of Health State.

AakashMSFT_0-1585744699370.png

 

 

Issue with Alert Closure

=============================

When an alert is closed for the below 2 scenarios, user would get an error "Object reference not set to an instance of an object.". Let us look at these scenarios in details.

AakashMSFT_1-1585744699373.png

 

 

Scene 1

  1. User creates a monitor but disabled the option to "Generate an alert for this monitor".
  2. User sets an override to generate an alert
  3. After an alert is generated, if user tries to close it - oh oh .. Error

 

AakashMSFT_2-1585744699365.png

 

 

 

Scene 2

  1. User creates a monitor with (enabled) the option to "Generate an alert for this monitor".
  2. Once an alert is generated, User disables the option to "Generate an alert for this monitor".
  3. Now, if a `user tries to close the alert -- Error

 

AakashMSFT_3-1585744699360.png

 

 

Fix: Alerts can now be closed if the underlying Monitor's Alerting i.e. "Generate an alert for this monitor" is disabled.

 

 

Improper message on Web Console when closing Alert

==============================

When a user tries to close an Alert of an unhealthy Monitor from the (legacy) Alert View, a pop-up with random text was displayed. User had no idea what just happened.

 

Fix: Message on Pop-up is meaningful now.

 

AakashMSFT_4-1585744699367.png

 

 

Automatic Alert Resolution

=================================

On the Operations Console of SCOM 2019, we have a feature which closes any alerts after certain period of time based on the settings and it is called Automatic Alert Resolution (Operations Console > Administration > Settings). Upon double clicking this feature, we found that Alerts for unhealthy monitors were closed even though SCOM 2019 brought in this change.

 

Fix: We got in a couple of changes for Alert grooming.

1. Segregation of Rule based alerts and monitor based alerts on Automatic Alert Resolution

 

Current Behavior

After installing KB4551468 Hotfix

AakashMSFT_5-1585744699372.png AakashMSFT_6-1585744699368.png

 

2. Alert from Monitors cannot be closed until monitor is healthy.

 

 

Got Feedback on SCOM? Let us know: https://aka.ms/SCOMFeedback

@AakashMSFT @Vithalprasad Gaitonde @NehaGarg