Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

Looking for advice on grouping Dynatrace technical services into business sub-components

wijayantha8
Kilo Contributor

Hi everyone,

I’m looking for some advice on the best way to model application sub-components in ServiceNow ITOM.

We currently ingest application and infrastructure data from Dynatrace into ServiceNow using the Service Graph Connector.

Our current service structure is:

wijayantha8_0-1785432568615.png

The current gap is that there is no logical layer between the main application service and the detailed technical components.

For example, one main application may contain business or functional areas such as:

wijayantha8_1-1785432601670.png

Dynatrace can identify and monitor technical entities such as services, process groups, process instances and hosts. However, it does not know which of these technical entities belong to a particular business sub-component. This information would need to come from the application owners.

One option we are considering is introducing a Tier 2 Component Service layer:

wijayantha8_2-1785432632883.png

The possible approach would be:

  1. The application team identifies which Dynatrace services or process groups belong to each sub-component.
  2. The monitoring team applies a common tag to the relevant Dynatrace entities.
  3. The Service Graph Connector brings the tags into ServiceNow.
  4. ServiceNow uses the tags to group the technical CIs under the correct Component Service.
  5. The Component Service could then support impact visibility, alert routing and incident assignment.

However, Tier 2 is only an option we are considering. We are open to other solutions that may be more suitable or follow ServiceNow best practices.

We would appreciate advice on the following:

  1. Is adding a Tier 2 Component Service layer suitable for this requirement?
  2. Is there a better ServiceNow or CSDM approach for representing these sub-components?
  3. Can tag-based Service Mapping be used effectively for this purpose?
  4. Which Dynatrace entities should normally be tagged—services, process groups, applications or another entity type?
  5. Can ServiceNow use the tags while still following the existing CI relationships and technical topology?
  6. Are there any common limitations or problems with this approach?
  7. Has anyone implemented a similar model using the Dynatrace Service Graph Connector?

We would be grateful for any recommendations, design examples or lessons learned from similar implementations.

Thanks in advance.

0 REPLIES 0