Agent auto-naming is causing logs from one servant to overwrite the log of another

Products

• DX Application Performance Management

Issue/Introduction

It appears the EM is overwriting the agent logs of  _2, but the log files from _1 do not exist.

 

Environment

Agent Release 24.10.1.5 (Build 990005)
Using Java VM version "IBM J9 VM 1.8.0_451" from IBM Corporation
Parsed JVM version as CURRENT [java.version = 1.8]

Resolution

This is what is happening.

Let's say you have an App called App1, with 2 Servants. From the description, both share the same Agent folder

When the App started, both Servants will start with same name App1, so the log will be renamed to ...App1.log. And the log will contain logs for both Agents.

Later one of them was asked by MOM to rename to App1-1 to enforce unique name. Then the log will be renamed to ...App1_1.log.

The other one after a re-connect, due to timing, might be asked to rename to App1-2. The log will be renamed to ...App1_2.log, still containing logs for both Agents. This is what you see.

There is no fixed mapping between the Servant index and Agent name. Servant 1 may be App1-1 or App1-2 at different time. So there is no point separating logs either.