Hi,
I have a issue where [N] gets appended to the agent name, this causes confusion when you are grouping by agent name in any dashlet because you will get two entries for any one agent. In this example you can see st_wx112 and st_wx113 with and without [1].
What seems to happen is that the agent goes down (lost network, restart of server, ..), and before DT's record of this agent times out it connects again. Since the agent name is already connected DT appends a number to the name since <name> already is connected.
Examples of problems this causes:
Is there a way to solve/work around this issue?
Thanks,
Ole
Answer by Markus B. ·
We have recently seen another report of the same issue - turning off the indexing feature works around the problem.
You can also try to change the restart sequence on the agent to avoid this timing issue.
We will be investigating this internally to check for possible improvements of the server-side agent registration sequence.
I think that's a good idea, I have seen this feature at work many times - including on the DT Advanced course Problem is, most of the times I've seen this its experienced as a bug rather than a feature. You might want to consider revising the true => false default setting or revise the timing.
Thanks,
Ole
JANUARY 15, 3:00 PM GMT / 10:00 AM ET
How to evaluate the Appmon agents Load on Application servers ?
Moving agents to another System Profile
IIB - IBM Integration Bus instrumentation: custom sensors/External service API ignored
.net agent name include PID or USER
Bootstrap agent does not use DT_STORAGE for storing its collector peer list