.Net 1.1 Auto Sensors and Tagging problem
Hi,
I have a SUD which is based on a .Net Framework 1.1 application.
I am experiencing 2 issues with it:
1. In the PurePath call tree I can only see the Methods which have predefined Sensors, I cant see anything else down the call stack. It seems like the Auto Sensors functionality is not working at all or properly in this environment.
2. The different Tagging sensors (Web Services, Remoting) aren't creating a single Transaction Flow across tiers even though I have a dT .Net Agent on both "client" and "server" side of different Web Service and Remoting calls in this application.
Has anyone ever run into these issues?
Thanks,
Elad.
Hi All,
First let me say, wow! This was my first post on here and I am quite overwhelmed with all the great info and assistance.
I realized the Auto Sensor functionality was misbehaving under 1.1 when I tried to do a CPU Sampling and it said no supported agents were avaiable.
Regarding the tagging issue, I need to investigate this further following your input, I am starting to believe I might be missing an agent(s) on some endpoints. This is mainly due to the fact that as per Rob's question, I cannot seem to find the "server" PurePath, only the "clients" call's PurePaths.
Regards,
Elad.
Elad.
hi Elad,
for #1: auto-sensors won't work with .NET 1.1, because the required functionality was not available then.
for #2: based on the available information we cannot make a qualified statement about this issue. we'd need more information like the technologies in use. usually i'd ask for a CPU sampling session, but unfortunately that's also not possible on .NET 1.1.
please keep in mind - as Reinhard already said - that .NET 1.1 mainstream support already ended in 2008 and that dynaTrace will de-support .NET 1.1 with the next release.
i'd be curious why .NET 1.1 is stilled used in this environment?
best,
Christian
Note that .Net 1.1 has reached it's mainstream support end of 2008. As Rob mentioned there are some limitations with older versions of .Net that hinder to use advanced techniques and impose problems with autosensors. Therefore .Net 1.1 will be de-supported in upcoming releases of dynaTrace.
Reinhard
Elad,
For #1, are you sure auto-sensors are enabled? If this was a migrated system profile (from 3.5.x) for example, it won't be enabled until you have fully addessed any migration issues. To see if it's enabled, edit your system profile, go to your .NET agent group(s), select Agent Mapping, click the "Advanced" button, and review the "Add extended information" checkbox in the "Extended PurePath Information" section.
For #2: There can be issues with that, but there is not enough information from your message for me to tell. One note: We do support it, but .NET 1.1 is quite old (circa 2003). I can imagine that there could be issues with this. Are you seeing just a single PP representing the "client" side of the transaction, or are you seeing two PPs, one for the "client" and one for the "server"?
Rob
