A developer is using Instana Unbounded Analytics to find all MongoDB calls from the 'inventory-service' that took longer than 500ms in the past 24 hours. Which approach should they use?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Unbounded Analytics in Instana's Calls view allows simultaneous application of multiple filters—service name, call technology type (MongoDB), and duration threshold—to retrieve exactly the granular call records matching all conditions. This is the purpose-built tool for ad-hoc trace-level exploration with combined filters. The Infrastructure view provides host-level metrics rather than individual call records.
Full explanation below image
Full Explanation
Unbounded Analytics in Instana's Calls view allows simultaneous application of multiple filters—service name, call technology type (MongoDB), and duration threshold—to retrieve exactly the granular call records matching all conditions. This is the purpose-built tool for ad-hoc trace-level exploration with combined filters. The Infrastructure view provides host-level metrics rather than individual call records. The Service Map shows high-level aggregated service health, not individual call-level records with combined duration filters. The correct answer is 'Apply filters for service=inventory-service, technology=MongoDB, and duration greater than 500ms in the Calls analytics view'. The incorrect options — 'Filter by host tag and database type in the Infrastructure metrics view', 'Use the Service Map to select the MongoDB node and filter the displayed calls by latency', 'Create an SLI based on MongoDB call duration and review the SLO compliance dashboard' — 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.