Best Practice: Management Pack Elements should have display strings

 

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 all MP elements to have display strings.

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 display names, the Operations Console will use Element ID names to identify MP elements. Element ID names are typically geared toward MP authors and product developers, not operators. Having Element IDs and identifiers for functionality creates customer dissatisfaction with the management pack.

How do I fix this in my MP?

Using the Authoring Console:

1.        In the Authoring console, all elements have a display name field. Ensure that this field is filled in. The Authoring Console will not let you proceed with creating an element without providing a display name.

Using XML:

     < UnitMonitor ID = " Microsoft.Windows.Server.2008.LogicalDisk.AvailabilityHealth" Accessibility =" Public" Enabled =" onEssentialMonitoring" Target =" Server2008!Microsoft.Windows.Server.2008.LogicalDisk" ParentMonitorID =" SystemHealth!System.Health.AvailabilityState" Remotable =" true" Priority =" Normal" TypeID =" Microsoft.Windows.Server.2008.LogicalDisk.Monitortype" ConfirmDelivery =" false" >

       …

     </ UnitMonitor >

…

       < DisplayString ElementID = " Microsoft.Windows.Server.2008.LogicalDisk.AvailabilityHealth" >

          < Name > Logical Disk Availability </ Name >

         < Description > Monitors the availability of this logical disk. </ Description >

       </ DisplayString >