We have a business service. This service runs on several blocks (on several different hosts).
From the point of view of Business - Service is one and it provides the end-service for users. Practically, different branches of users or different versions of the application can be launched on different blocks.
From the point of view of Suppor and Operation - they need to evaluate the work of different block and for the whole service
We have created a dashboard.
Added service and service&request widgets
Created a managemet zone by block and by whole service
1. Management zone do not filter service&request widgets
it does not filter it even if you select a management zone simply by infrastructure hosts
Examle - MZ = only Windows but service is displaing!
2. Managet zone by block control do not work.
If I select different Managemt Zone by blocks and add service metrics to the custom chart, they are not filtered when zones are selected
Could you please tell me is it a bug or am I doing something wrong ?
Solved! Go to Solution.
I would like to give you a bit more context for what is happening. In the Dynatrace world of entity mapping, we create some logical groupings for related entities. We have the direct (tangible) mapping of Host > Process > Service Instance. However, within the same host group, if we see the same Process running on multiple hosts we will create some more (logical) groupings: Process Group (a logical group of all related Process entities from the same host group) and Service (all related Service Instances from the same Process Group).
Here's a diagram to help visualise it (blue are tangible entities, purple are logical groupings):
With this in mind, when you are creating Management Zones, take note of what entities you are applying it to; the rules work with Process Groups and Services which will inadvertedly contain multiple Processes and Service Instances. Hence even if you have regular charts, you are not able to work with the filtering per instance or per Process.
What I would recommend for your dashboarding requirements is to create either a Multi Dimensional Analysis view which allows you to split the data per Service Instance, or use the existing Service Details view and add a filter by Service Instance. Neither of these can be displayed directly on a dashboard, but both of them can be referenced by links. So you can have your general Service/Request chart on the dashboard, and links next to it to drill down to the more granular views.
With the Multi Dimensional Analysis view, you have the advantage that other team members will also be able to access it from the Service's overview page instead of requiring access to the dashboard.
I hope this helps.