An organisation already scrapes application metrics with Prometheus and now wants them alongside Instana's own data. What is the appropriate approach?
Select an answer to reveal the explanation.
Short Explanation
Keep the Prometheus pipeline you already trust and bring its metrics into Instana. That way the data joins the rest of the observability picture instead of living on its own island.
Full Explanation
The appropriate approach is integrating the Prometheus metrics into Instana so the existing pipeline is preserved and its data appears with the rest of the observability picture. Prometheus integration exists precisely for organisations with an established metrics pipeline. Bringing that data into Instana avoids re-instrumenting while ending the split between two separate views of the same systems.
Replacing trace context with Prometheus labels so both systems share one identifier scheme is incorrect because trace context and metric labels serve different purposes; trace context propagates request identity across services and cannot be replaced by labels.
Relying on Prometheus to collect the application's distributed traces as well is incorrect because Prometheus is a metrics system; it does not collect distributed traces, which is a significant part of what Instana contributes.
Importing every available metric without deciding which labels to carry across is incorrect because unplanned label import produces high-cardinality data that is expensive to store and awkward to query.
For the exam, position Prometheus integration as metric ingestion that complements tracing rather than replacing it.