After installing the Instana host agent on a Linux server running Apache Tomcat, a junior administrator can see host-level CPU and memory metrics in Instana, but Tomcat-specific metrics (heap usage, thread count, request rate) are not appearing. What is the most likely explanation?

Instana's built-in Tomcat sensor collects metrics via the JMX interface exposed by Tomcat. If JMX is disabled on Tomcat or the agent cannot connect to the JMX port due to configuration or network issues, Instana will see the host but not collect application-level Tomcat metrics. Tomcat monitoring is built into the standard Instana agent and does not require a separate license, manual process registration, or containerization. The correct answer is 'Tomcat metrics require JMX access; the administrator should verify JMX is enabled on Tomcat and the agent can connect to it'. The incorrect options — 'Tomcat monitoring requires a separately licensed Instana plugin that has not been purchased', 'Tomcat metrics only appear after the Tomcat process is manually registered in the Instana web UI', 'The Instana agent only monitors Tomcat when it is running inside a Docker container, not on bare metal' — 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.