Reconnecting / reenabling .NET agents
Hi,
Is there a way of re-enabling .NET agents when they have been disable because of ambigous agent mapping?
"Instrumentation disabled since the agent was not mapped into an agent group"
Hi
This message means that the agent is actually properly configured on your machine where you have your .NET Application. But - it is configured to use an Agent Name that currently doesnt map to any configuration in your dynatrace System Profiles. Everytime an agent starts up it connects to dynatrace using the confiugured name. If dynatrace doesnt expect an agent with that name (because its not configured) it will not instrument the agent.
All agent mappings can be found in the System Profile under your individual Agent Groups (=Agent Tiers Definitions). There is a section called Agent Mapping where you can define the name that dynatrace is looking for to map to that Tier.
Now - before I go into too many details I suggest you also check out the videos I recorded and put on youtube that explain how agents and how agent mappings work. check out the full list of all videos: http://bit.ly/dttutorials - and check out the one on "System Profiles Explained" and the one on "How Agents Work". You dont need to watch the whole thing as the full recording also includes the Q&A session. The first 10-15 minutes will do
Andi
The fix was to reboot the Web server. (the agent mapping was correct)
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
September 2017
Announcing Dynatrace's Community Member of the Month for September 2017, Tarun A.! Click here to read more! 
