It was suggested to open a case investigating why it takes nearly 5 minutes for metric data to populate in DX APM SaaS after an agent starts.
Is there anything that can be updated in the introscope agent profile to fix this?
Are there other areas of interest to check?
Release : APM SAAS
So it took 2 minutes from start of the Agent to connect to a Collector. Mostly because it attempts to determine the agent name.
The Agent connects to the Collector. Once that happens, metrics will start coming in. First your base metrics will appear, GC Heap, Agent stats, etc... Other metrics will start to appear once the application is exercised. Frontends are usually the last to appear generally because that part of the app must be exercised.
[INFO] [IntroscopeAgent.Agent] Agent Release 220.127.116.11 (Build 990049)
[INFO] [IntroscopeAgent.Agent] New list accepted
[INFO] [IntroscopeAgent.ConnectionThread] Connected to apmgw.dxi-na1.saas.broadcom.com:443,com.wily.isengard.client.transport.websocket.SSLWebSocketFactory in allowed mode.
Here we see that the agent name is still being determined and finally used.
[INFO] [IntroscopeAgent.Agent] Unable to automatically determine the Agent Name because: The Application Server naming mechanism is not yet available.
[INFO] [IntroscopeAgent.Agent] Unable to automatically determine the Agent name before the connection delay timeout.
[INFO] [IntroscopeAgent.Agent] Auto Agent Renaming is enabled and will check for a new Agent name from the Application Server every 10 minute(s).
[INFO] [IntroscopeAgent.Agent] Using the Agent name "Test" based on the "introscope.agent.agentName" property in the Introscope Agent Profile.
[INFO] [IntroscopeAgent.Agent] Initial agent name set to Test
Please reduce the value of this property in the Agent Profile to 10 seconds. This requires a restart to take effect.