Agents not mapping to correct agent group

Thanks for your help everyone!

Yekaterina,

I'd try changing the mapping rules to 'equals' rather than 'starts with'.

-- Graeme

I believe you have at least two options that might work for you:

1. Use "equals" with both "Scheduler", and "SchedulerLegacy" to avoid the "starts with" issue
2. If they run on different hosts, you can alternatively use the Agent Host as part of the mapping to be more selective

Once you change the mapping, there would need to be an application restart for the new mapping to take effect.  

The historical data would remain under the agent groups they are under now, and would then start showing up under the new agent groups after you get the mapping fixed.

HTH,

dave

The "Scheduler[" wouldn't help as the [SchedulerApp] is appended to the end of the agent group after it is connected.  andreas.grabner@dynatrace.com is there any sort of priority for agent mapping if not I think that would be a good RFE to be able to change that.

We have 2 .NET apps with similar names, "Scheduler" and "SchedulerLegacy". The agent names look like this: "Scheduler[SchedulerApp]..." and "SchedulerLegacy[SchedulerLegApp]...". The agents for each app are mapped into their own respective agent groups, but both are mapped using the setting "Agent Name" and the condition "starts with 'Scheduler'". As a result of this, both sets of agents are ending up under the "Scheduler" agent group, with no data under the "SchedulerLegacy" agent group. Will this be resolved by modifying the condition for the Scheduler app to read something like this: Agent Name starts with "Scheduler[" or some similar modification to the conditions of these groups? If yes, can the agent mapping condition be changed without modifying the agents themselves, recycling the app pools, or losing any historical data for those agents?