A DevOps engineer needs to configure the Instana agent to exclude HTTP health-check endpoints such as /health and /metrics from being traced in a Java application. These calls are polluting trace data and skewing latency metrics. In which file and section should this endpoint exclusion be configured?
Select an answer to reveal the explanation.
Short Explanation
You configure this in configuration.yaml under the com.instana.plugin.javatrace section, where the ignore-endpoints list tells the Java tracer to skip spans for paths like /health and /metrics. That keeps noisy health checks out of trace data and latency metrics.
Full Explanation
configuration.yaml hosts all plugin-specific settings, and the com.instana.plugin.javatrace section controls Java tracing behavior, including endpoint exclusions. The ignore-endpoints list within that section instructs the Java tracer to skip generating spans for the specified URL paths, so HTTP health-check endpoints such as /health and /metrics are excluded from trace data and latency metrics. The com.instana.agent.main.sender.Backend.cfg file under the backend.http.ignore block is wrong because that file handles connectivity only and has no tracing control capability. The instana-agent.env file by appending exclusion paths to JAVA_OPTS is wrong because that approach does not align with IBM Instana's architecture or recommended practices for configuring Java tracing exclusions. The agent.properties file under the trace.exclusions property is wrong because that approach also does not align with IBM Instana's architecture or recommended practices for this scenario. Understanding this concept is essential for the Domain 2: Configuration domain of the IBM Instana Observability certification.