Best Practice: Alerts should have a name and description field


What does this best practice check for?

There are certain management pack elements for which it is considered high-priority for them to have associated display names. As a best practice, it is high-priority for alerts to have the name and description field completed.

Why is it important to follow this best practice? What is the impact of not following this best practice?

The display name gives the end-user a friendly name to identify MP elements without element IDs. The descriptions are also important to have in alerts as end-users usethese when trolling the alert view to determine what a particular issue actually is without having to drill into knowledge. Not having a description field increases the amount of work that the end-user has to do in order to do their jobs.

How do I fix this in my MP?

Using the Authoring Console:

1.        In the Authoring console, for monitors that will produce alert, click on Properties, and go to the Alerting tab. Ensure that an Alert name and Alert description are specified.

2.        In the Authoring Console, for rules that generate alerts,ensure that you have specified an alert name and alert description when building an alerting rule.

Using XML:

       < DisplayString ElementID = " AlertMessageID1174ddb52fa84d038200f297c5aa47dc" >

          < Name > AD CS Key Archival and Recovery </ Name >

          < Description > Event Description: {0} </ Description >

       </ DisplayString >