asynchrounous web request split into two parts instead of one
Description issue: Async Web request split in two
IWS_Get_Drivers = Web request (1ms) | SyncMethod... = async execute (99ms)
I should expect one call IWS_GET_Drivers (100ms)
Alerts
If I look to dynatrace diagnose --> lost purepath info
I think I have an issue in configure the agent mapping to my system profile.
I must say that I not completely understand how to configure it.
----------------------------------------
This are the .NET processes that I want to monitor (2x wcf, 1 wcf as a service)
I created a profile and I will use one agent group for all my processes (loadTest_fleetService), correct?
the agent name = name in dtwsagent.ini (LoadTestWebserver_MonitoringLoadTest)
Agent configuration
A month ago we did a poc with Chris G, I remember we had a issue closely to this one,
then Chris changed the name in the dtwsagent.ini (is guess to have a correct mapping).
Thx
Best Answer
Thanks for the session.
I am not sure if the incorrectly mapped web server agent is the problem here - but it could - and also could be the reason for breaking your paths. Your Web Server Agent uses the name LoadTestWebServer_MonitoringLoadTest. This would map to your Agent Group called LoadTest_FleetService. It should map based on the name - but - I assume that you started the dynaTrace Web Server Agent Windows Service before you configured that tier. So - try to restart your dynaTrace Web Server Agent Windows Service.
The other thing though is that your Agent Group Definition doesnt place Web Server or User Experience Sensor. I assume you want to use UEM as well? In that case you need to make sure to place these Sensor Packs in your Agent Group - otherwise the WEb Server Agent Module that you load in IIS wont collect data. A best practice here though is to create a separate Agent Group. I would call it "Web Server". Give it a different Agent Name and use that agent name as well in your dtwsagent. With that you have a clean separation between Web Server and ASP.NET.
Please try that first and see if that makes a difference
What is odd though is that you have a lot of these PurePaths that time out (running longer than 10minutes). Thats why you see the skipped events because these transactions take that long and dynaTrace simply stops these purepaths. When these transactions in fact continue in your app and keep sending data these "events" (the data we collect) cannot be assigned to a PurePath anylonger (because its timed-out). Therefore we skip these events. Question is whether you really have that long running transactions or whethert this is a dynaTrace Problem.
If fixing the Web Server Agent Mapping doesnt change the situation I suggest to open a support ticket. Point them to this forum post. What is also odd - and why I think a support ticket will be good - is the fact that you dont see any auto sensor data in your long running PurePaths. That is a strange thing because typcially we always have Auto Sensor data when transactions run that long
hope this helps
It looks like you did everything right on the .NET Side. Could you export a couple of these PurePaths and attach them as well? Also - can you post a screenshot of your Agent Overview DAshlet? That will show if you have issues with your AGent Mapping for your dtwsagent.ini
Andi
The agent with yellow remarks is an old one (created in poc with Chris G.), interesting is the group contains all the processes (FWS,IWS).
I would call it "Web Server". Give it a different Agent Name and use that agent name as well in your dtwsagent.
I still don't understand how the mapping works
If i create a agent group --> click on agent mapping --> Agent name
- is this value always the name of the agent running one a server?
- In other words, is this value always the value from the dtwsagent.ini (LoadTestWebserver_MonitoringLoadTest)?
i' m asking this because Chris Geebelen did following in the poc:
- Create agent group (webserver), agent name equal to name in dtwsagent.ini
- Create agent group(.NET webservices), agent name = X, X value placed in agent configuration agent1.png
- Create agent group(.NET webservices), ...
So what is the definition of a agent:
- Agent name in agent group, So dtwsagent contains multiple agent names (groups)
- Name of dtwsagent
What is used to corrolated?
Other question,
- i have five lisences, can i monitor 5 servers with on each server, for example 50 agents groups?
- Is theire documentation on how to configure agents, groups, ...
- Is system profile name importent for correlation?
Thx
I reached out to Chris to see whether he can also add his thoughts on this
Looking at the Exportet Session of yours and the System Profile I couldnt see the Agent Tier for the Web Server - maybe you deleted it accidentially?
To answer your question about Agent, Agent Group, ...
A System Profile defines one or many Agent Groups where an Agent Group can be considered a "Logical Tier" of your application, e.g: Web Server, Frontend Server, Backend Services, ...
In order to know which Agent (=.NET, Java, Web Server, ...) maps to which Agent Group you have to give every agent a name. This name is provided by either the command line (for Java Agents), the .NET Configuration Tool (for .NET Agents) or the dtwsagent.ini file (for Web Server Agents).
When an Agent launches and registers on the dynaTrace Server it basically says: "Here I am - and my name is ABCD". Then dynaTrace looks into all your System Profiles and tries to find the Agent Group that defines an Agent Mapping that maps to that name. If there is no match the Agent will not do anything in the app and the agent wiill show up with the little warning icon in the Agent Overview telling you that there is no matching System Profile.
For Web Server Agents the default name of the Agent configured in dtwsagent.ini is "dtwsagent.ini". When you use the Add Tier Wizard to define your Tiers (=Agent Groups) for your app the Wizard typically tells you to change the config in dtwsagent.ini so that the name also reflects the name of your logical tier. You typically have a name similar to "WebServer_MySystemProfile".
So - how to fix your situation?
a) check if your System Profile has an Agent Group for your Web Server -> if not - use the Add Tier Wizard to add it or add it manually.
b) Make sure the agent name in dtwsagent.ini matches what you have specified in your System Profile
c) Restart the dynaTrace Web Server Agent Windows Service. This is the Web Server Agent that - during startup- will read the dtwsagent.ini and with that knows which name to use
Andi
Hello Andreas,
I have further investigated this issue,I had also a Phone call with Chris G,
i have done some config modifications, maybe you can point out something that is wrong,i gues it may be a bug,
-------------------------------------------------------------------
Example of one agent group --> LoadTest_IWS
Alias + Name + Agent Name: LoadTestWebServer_MonitoringLoadTest_IWS
Her we had an issue because all our agent groups had the same name (@ChrisG)
The agent configuration the above agent group
The active sensors for the above agent group
Agent overview
Issue: sometimes we have a correct connection between async call and execute parth, sometimes not
Example of correct purepath
Example of incorrect purepath,
Some time later above changes (green circle), but still two parts
I have als added pure path export, are there any things we can do, or should i create ticket?
IWSWebServiceExport.dts FWSWebServiceExport.dts
Thx Andreas
Hi. I am currently travelling and limited on time to have a closer look.
One thought that I have: are you sure you have instrumented EVERY .NET Process? In case you have a load-balanced cluster make sure that all nodes are instrumented. If not it would explain that you see broken PurePaths in case you dont have full visilbily because not all .NET Processes run an agent.
If you need faster help you may want to reach out to support
