Host Agent Installation
TABLE OF CONTENTS
Depending on what type of systems you want to monitor and whether you want dynamic or static host agents, there are multiple options available to you. For some platforms, like Kubernetes, there is more than one way to get the Instana host agents running, and we offer specialized, streamlined setups for some managed services by AWS, Google Cloud, Azure and others.
Some of the components of the host agent run outside of the host agent process and connect to it using the local network. Ensuring correct communication between agents and sensors may require configurations in containerized setups.
The table below lists the ports that have to be opened to reach the agent process. Apart from the default 42699 port, other ports are required based on the languages you want to trace.
|JVM tracing (Java, Kotlin, Scala, Clojure) and sensors for technologies running on the JVM1||All ephemeral ports|
|Crystal Sensor||42699||Environment Variable|
|Envoy, NGINX and other Proxies tracing||42699||Environment Variable|
|Go Sensor||42699||Environment Variable|
|Node.js Sensor||42699||Environment Variable|
|PHP Sensor||16816||PHP configuration|
|Python Sensor||42699||Environment Variable|
|Ruby Sensor||42699||Environment Variable|
In Kubernetes environments the network policy must allow a connection between agent pods and service pods so that external sensors can reach the agent, and vice versa.
1 Spring Boot, Dropwizard, Cassandra, Elasticsearch, Neo4j, Hazelcast, ActiveMQ, Kafka, Finagle, Tomcat, Jetty, JBoss, WebLogic, WebSphere, Glassfish, Hadoop, HBase, Solr, Spark, Jira, Liferay, Mule, Ping Directory, Jenkins