Adding Top-Level Object Types (SCOM)

By default, the Management Pack for SCOM recognizes a default list of object types (i.e., resource kinds). (See: Resource Kinds and Relationships (SCOM)). You can configure additional top-level object types using the topLevelResourceKinds property in the scom.properties file. SCOM entities that are not configured as top-level types appear as metric groups under the nearest top-level parent entity. If multiple levels of objects that are not top-level appear under a top-level object, the Management Pack for SCOM creates groups within groups. EXAMPLE: if an entity named mydb of type Microsoft.SQLServer.Database is not configured as a top-level type, it appears as an instanced group named Microsoft.SQLServer.Database:mydb. The Management Pack will assign all metrics for mydb to the instanced group.

Prerequisites

• Creating an Adapter Instance (SCOM)

Procedure

1. The query returns all SCOM entities.
   1. For a database, run the query SELECT Name FROM ManagedTypeView ORDER BY Name

   2. For a data warehouse, run the query SELECT ManagedEntityTypeSystemName FROM vManagedEntityType ORDER BY ManagedEntityTypeSystemName

2. From the query results, find the entity types to add as a top-level object type.
3. Edit the scom.properties file to add the value(s) to the comma-separated list in the topLevelResourceKinds property.
4. Save your changes and close the scom.properties file.
5. Optionally, add the object type to the categories.properties file, assigning it to the category group Appliances, Applications, Operating Systems, Services, Servers, or Virtualization.
6. Stop and restart collection for the adapter instance.