search cancel

DX APM APMIA agent blocking 8080 port by default (Question Case)

book

Article ID: 253082

calendar_today

Updated On:

Products

CA Application Performance Management SaaS

Issue/Introduction

We upgraded APMIA agents to 21.12 version on Linux servers and our application teams started raising incident stating that their application is not starting after APMIA agent upgrade.

While analyzing the logs we observed that APMIA agents are blocking port 8080 by default.

1. Could you please help us understand why port 8080 is being blocked by default?

2. what are the configurations that we need to take care if we need to change it to different port?

3. What are the metrics we loose if we disable this port on IntroscopeAgent.profile ?

4. What components of APMIA is using this port and for what metrics collection?

Below is the property in APMIA profile file.

# Changing this property requires restarting the Monitored Process
introscope.epagent.config.httpServerPort=8080

For validation you can download the APMIA agent from ACC from any tenants.

Environment

Release : SAAS

Resolution

1. Could you please help us understand why port 8080 is being blocked by default?
This is the default port used by the APMIA Http Server Port.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/infrastructure-agent/epagent-plug-ins/standalone-epagent/install-and-configure-the-standalone-epagent/configure-the-standalone-epagent-for-network-data-sources.html

You may have missed this warning
Using port 8080 for the introscope.epagent.config.httpServerPort property value causes a port conflict when port 8080 is being used by another web server or application server. In particular, when installing the Standalone EPAgent on the same server as the Enterprise Manager when WebView is running on its default port 8080. In this situation, a conflict occurs.

I recommend looking at the following for overviews on ports 
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/installing/apm-installation/pre-installation-requirements/open-apm-ports.html

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/ca-apm-sizing-and-performance/system-information-and-requirements/apm-ports.html

2. what are the configurations that we need to take care if we need to change it to different port?
introscope.epagent.config.httpServerPort=newport or comment out 
#introscope.epagent.config.httpServerPort

3. What are the metrics we lose if we disable this port on IntroscopeAgent.profile ?

Anything that comes in using a HTTP GET
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/infrastructure-agent/epagent-plug-ins/standalone-epagent/install-and-configure-the-standalone-epagent/configure-the-standalone-epagent-for-network-data-sources.html

Also anything using a REST API
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/infrastructure-agent/epagent-plug-ins/configure-epagent-network-ports/enable-the-epagent-plug-ins-restful-interface.html

Metrics are covered here.

4. What components of APMIA is using this port and for what metrics collection?

Below is the property in APMIA profile file.

# Changing this property requires restarting the Monitored Process
introscope.epagent.config.httpServerPort=8080

From Rob:
The HTTP 8080 is from old EPA agent. In older version it was in separate bundle I asked you to remove that when creating the package. In recent release they put it on by default when the AC migrated that logic from separate bundle (the one you removed) to main APMIA.  

You will not lose any metrics as you have not been using unless you are using APM for API, APM for SiteMinder, Nginx that call for it.