Default ports used by agents and data collectors

Edit online

Various ports are used for communication between the Cloud APM component and the application or system (either local or remote) that is being monitored. In most cases, default ports are provided to facilitate configuration. Most defaults can be customized by using configuration parameters.

Table 1 lists the default ports that are used by the Cloud APM agents and data collectors to communicate with the applications or systems that they are monitoring. N/A in the table indicates one of the following situations:
  • The agent or data collector does not use any port to communicate with the monitored application or system.
  • The port used for communication is determined by configuration of the monitored application.
  • Ports used by the agent or data collector are dynamically assigned and no static defaults are provided.
  • All ports to be used must be specified by the user and no defaults are provided.

For the ports used for communication between the Cloud APM server and the agents or data collectors, see Cloud APM server ports.

Table 1. Default ports used by agents and data collectors
Agents and data collectors Default ports Configurable Local Remote
Amazon EC2 agent
  • TCP port 80 (for HTTP)
  • TCP port 443 (for HTTPS)
 N/A Yes No
Amazon ELB agent
  • TCP port 80 (for HTTP)
  • TCP port 443 (for HTTPS)
 N/A No No
Azure Compute agent
  • TCP port 80 (for HTTP)
  • TCP port 443 (for HTTPS)
 No No No
Cassandra agent 7199 (for JMX server, local and remote) Yes Yes Yes
Cisco UCS agent
  • TCP port 80 (for HTTP)
  • TCP port 443 (for HTTPS)
 No Yes No
Citrix VDI agent For PowerShell calls:
  • 5985 (for HTTP)
  • 5986 (for HTTPS)
 Yes Yes Yes
Db2® agent
  • 50000 (default port of Db2 server)
  • Remote Monitoring supported: Uses port number given by the user while cataloging the remote server instance.
 Yes Yes Yes
DataPower® agent 5550 (for connecting to remote DataPower appliance) Yes No Yes
Hadoop agent
  • Local monitoring: CP_PORT environment variable value
  • Remote monitoring:
    • 50070 (Standby Namenode)
    • 50090 (Secondary Namenode)
    • 8088 (ResourceManager)
    • 19888 (JobHistory Server)
    • 8080 (Ambari)
 Yes Yes Yes
HMC Base agent 12443 (for downloading SDK from HMC) No Yes No
HTTP Server agent HTTP server might be configured to different port, but the agent itself has no default port. N/A Yes No
IBM® Cloud agent Outgoing connection to api.softlayer.com port 443. N/A No Yes
IBM Integration Bus agent N/A N/A Yes No
Internet Service Monitoring For databridge:
  • 9510
  • 9520
 Yes No Yes
DataStage® agent
  • 9443 (WAS HTTPS port)
  • 50000 (Database JDBC port)
  • 1433 (Microsoft SQL)
  • 1521 (Oracle)
 Yes Yes Yes
J2SE data collector N/A N/A No No
JBoss® agent Varies according to the version of the JBoss server:
  • 9990
  • 9994
  • 9999
 No Yes No
Liberty data collector N/A N/A No No
Linux® KVM agent
  • 8080 (for HTTP)
  • 8443 (for HTTPS)
 Yes Yes No
Linux OS agent 22 (for remote log monitoring with SSH) Yes Yes No
MariaDB agent 3306 Yes Yes Yes
Microsoft Active Directory agent The port number depends on the listener setting for monitoring usage. N/A Yes Yes
Microsoft Cluster Server agent N/A N/A No No
Microsoft Exchange Server agent N/A N/A No No
Microsoft Hyper-V Server agent N/A N/A No No
Microsoft IIS agent N/A N/A No No
Microsoft .NET agent To send transaction tracking data, port 5456 is used by default. Yes Yes No
Microsoft Office 365 agent 7799 (for Skype synthetic transaction) Yes Yes No
Microsoft SharePoint Server agent 1433 (for SQL server) No Yes Yes
Microsoft SQL Server agent 1433 (default of SQL server) Yes (by COLL_PORT) Yes No
MQ Appliance agent
  • 162 (for receiving SNMP events)
  • 5554 (for connecting to MQ Appliances)
 Yes Yes Yes
MongoDB agent
  • 27017 (for single instance)
  • 27019 (for cluster)
 Yes Yes No
MySQL agent 3306 (for JDBC connection) Yes Yes Yes
NetApp Storage agent For remote monitoring:
  • 8088
  • 8488
  • 443
  • 8443
 No No Yes
Node.js agent 63336 Yes Yes No
Node.js data collector N/A N/A No No
OpenStack agent 5000 (for connecting OpenStack identity service) Yes No Yes
Oracle Database agent 1521 (for SQL connection) Yes Yes No
PHP agent
  • Apache connection
  • Port number is based on the Apache configuration
 Yes Yes No
PostgreSQL agent 5432 (for JDBC connection) Yes Yes Yes
Python data collector N/A N/A No No
RabbitMQ agent Port number where the RabbitMQ management plug-in is enabled (local and remote): 15672 Yes Yes Yes
Response Time Monitoring Agent
  • Package analyzer model monitors HTTP transactions at port 80.
  • HTTP server model monitors all ports.
 Yes Yes No
Ruby agent Dynamically generated N/A Yes No
Ruby data collector N/A N/A No No
SAP agent 33nn (where nn is the SAP instance number) No Yes No
SAP HANA Database agent Default: 30013. Range: 30013-39913. Yes Yes No
SAP NetWeaver Java™ Stack agent Default: 50004. Range: 50004-59904. Yes Yes No
Siebel agent N/A N/A Yes No
Skype for Business Server agent (formerly known as Microsoft Lync Server agent)
  • Business server default port 5061
  • SQL server port 1433 (local or remote depending on environment).
 No Yes No
Sterling Connect Direct agent 1363 Yes No Yes
Sterling File Gateway agent 50000

The IBM B2B Integrator REST API port number and Database port number are both required and are configurable.

 Yes Yes Yes
Sybase agent 5000 N/A Yes No
Synthetic Playback agent
  • 4444 (for connecting internal selenium server)
  • Remote ports are specified in the http URL of monitored websites, typically HTTP 80 and HTTPS 443
 No Yes No
Tomcat agent 8686 (for Tomcat MBean server) Yes (by JMX port) Yes No
UNIX OS agent 22 (for remote log monitoring with SSH) Yes Yes No
VMware VI agent
  • 443 (for remote monitoring)
  • 80 (for local monitoring)
 No Yes Yes
WebLogic agent 7003 (JMX Management HTTP traffic) Yes Yes No
WebSphere® Applications agent
  • 63335 (for V8 monitoring agent)
  • 63336 (for V6 monitoring agent)
  • 63355 (for resource monitoring)
  • 5457 (for Transaction Framework Extension)
 Yes Yes No
WebSphere Infrastructure Manager agent N/A N/A Yes No
WebSphere MQ agent The port number depends on the listener setting for monitoring usage. N/A No Yes
Windows OS agent 22 (for remote log monitoring with SSH) Yes Yes No