DX Application Performance Management

Hello All,

I have some agents and they are reported on same server and some of them are reported as AgentName%1,AgentName%2,AgentName%3,AgentName%4,AgentName%5.

We used to give only following properties in 'IntroscopeAgent.profile' as shown below:-

introscope.agent.customProcessName=ProcessName

introscope.agent.defaultProcessName=UnknownProcess

introscope.agent.agentAutoNamingEnabled=true

introscope.agent.agentAutoNamingMaximumConnectionDelayInSeconds=120

introscope.agent.agentAutoRenamingIntervalInMinutes=5

I did not see any existing agent name with the same name which was trying to report in investigator.

Please help in understanding this concept.

Thanks

Vaibhav

Hi Vaibhav,

Although you have agentAutoNaming set to true, that is only valid for certain application servers (WebSphere, Weblogic, Jboss) and then it needs configuration for that to work (as per the Java Agent documentation)

We are relying on mechanisms in these app servers to get the name information back.

If all else fails, the agent will fall back on AgentName, so if all agents are using the same profile, a value %n is appended to the second, third, fourth etc  agent so you get unique information

Assuming these processes have separate JVM startup parameters you could do a few things.

1) Make separate copies of the IntroscopeAgent.profile with unique names and specify the name in this value if uncommented.

#introscope.agent.agentName=AgentName

in this case you should update the JVM parameters to point to the separate profiles.

2) Again assuming there is separate JVM parameters, you can specify the name directly there

So it would be something like -javaagent:<path to Agent.jar> -Dcom.wily.introscope.agentProfile=<path to agent Profile> -Dintroscope.agent.agentName=myagent1

3) If each instance has some specific Java property that is unique to it you could use this property in the agent profile

introscope.agent.agentNameSystemPropertyKey=

For example, if you look in the agent log, you can see all the properties used by the JVM, and just purely for example, we find this encoding value

8/14/15 11:56:49 AM BST [INFO] [IntroscopeAgent.Properties] file.encoding=Cp1252

you could then configure the agent profile like this

introscope.agent.agentNameSystemPropertyKey=file.encoding

and the agent would get the name of Cp1252.

You would be unlikely to use this exact property so I'm just giving this as a demonstration.

--

If these are .NET processes, it's more normal to have multiple processes, particularly where you have multiple worker processes in the same app pool, but it's rare that the naming feature doesn't discover a different name to AgentName.

Thanks,

David

Hello David,

Thanks for the information.

I am monitoring BW services and their are around 100 services reported on same server but with different name and they all are referring to same 'IntroscopeAgent.profile'.

It usually works fine. I called to CA support also and they replied if we already have BW services reported to investigator with the name 'abc' and then again any of the BW services is trying to report with the name 'abc' so it will report like 'AgentName%' but as per my understanding it should report like 'abc%1'.

Please suggest.

Thanks

Vaibhav

Hi Vaibhav,

As far as TIBCO is concerned, where you have a lot of processes on the same machine, we have seen that not all of the process names can be identified when the agent first connects, but eventually after the renaming period, the agent names can usually be renamed successfully - however the AgentName values will still show greyed out for about an hour until they are automatically remounted.

There is a similar discussion here Tibco BusinessWorks and agent names there is one suggestion about configuration that might help with the naming but it relates to TIBCO configuration itself but if none of those are suitable, you are meeting a current product limitation - I thought this had already been raised as an idea for product enhancement.

Thanks,

David

Hi David,

I have gone through with the post which you just referred to me.

Some of my process started around 4 days back but still in the same name AgentName%1 and so on.

Any suggestion how much time it will take to take his original name.

Thanks

Vaibhav

Hi Vaibhav,

Just checking what is your EM version?

Thanks

Lynn

Hi Lynn,

EM version is 9.5.2

Please suggest accordingly.

Thanks

Vaibhav

Vaibhav,

If you are seeing Agent being named as "AgentName%1" even though there is no other agent connected with same name "AgentName" then likely you are running into a known issue for which critical advisory was posted while back. Please see:

https://support.ca.com/phpdocs/7/5974/5974_TechnicalAdvisory_05-09-2014.pdf

Regarding your second question, once agent is assigned a particular name it will not get a different name unless it explicitly asks EM to do that or it restarts and reconnects to EM.

Regards,

Kulbir.

Thanks Kulbir

Hi Vaibhav,

In that case you might have hit a known problem which is only fixed in 9.6. See this previous thread: Automatic unmounting of agent fails

Hope it helps.

Lynn