A company's platform has 50+ microservices. The checkout team wants a focused Instana view showing only the services, calls, and metrics relevant to the checkout flow, without seeing unrelated infrastructure or other teams' services. What should they configure?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Application Perspectives are purpose-built in Instana to create scoped, dynamic views of a specific set of services and their dependencies, including a Service Map, dependency call flows, and aggregated metrics—all scoped to the defined service set. A custom dashboard can display metrics but does not provide the dynamic Service Map and call flow visualization. A separate tenant provides full data isolation but is an extreme measure for a simple team scoping requirement.
Full explanation below image
Full Explanation
Application Perspectives are purpose-built in Instana to create scoped, dynamic views of a specific set of services and their dependencies, including a Service Map, dependency call flows, and aggregated metrics—all scoped to the defined service set. A custom dashboard can display metrics but does not provide the dynamic Service Map and call flow visualization. A separate tenant provides full data isolation but is an extreme measure for a simple team scoping requirement. The correct answer is 'An Application Perspective scoped to checkout-related services using service names or tags'. The incorrect options — 'A custom dashboard with individual widgets filtered to show only checkout service metrics', 'A tag-based filter applied in the Infrastructure view saved as a personal bookmark', "A separate Instana tenant provisioned exclusively for the checkout team's use" — are wrong because they do not align with IBM Instana's architecture or recommended practices for this scenario. Understanding this concept is essential for the Domain 1: Operations domain of the IBM Instana Observability certification.