Browser Metrics

Hi,

Can you post the user-agent strings that are wrongly identified as IE7 or Firefox?

We use http://user-agent-string.info/ so you can check there what the recognized browser is based on the user-agent...

Best, Roman

Hello,

Use Case Number one is currently not covered by dT. Can you make an entry in our Product Feedback and Enhancement Requests Forum and describe the use case? Most important is for me, what you want to do with the information? Are you expecting different performance for IE7 and IE8 in comp. mode? Do you want to chart IE7 vs. IE8 comp. or would it be enough to filter the visits in the visit dashlet for IE8 comp.

2.) This needs more information. Can you send me the two (or more) user agents - or just put them into that thread?

thx, Alex

Thank you so much for the responses and feedback.  I will be providing shortly the user agents captured for each case.  It is very important for us to know exactly which browser is being used by our users because out web site has been desgined to be fully compatible with some web browsers and not all of them.  Although our web site is accessed by external users too, knowing the right browser being used can also help us ensure that internal users are not leveraging an old browser (IE 7) and have them update it accordingly.  Overall knowing the web browser distribution can also help us in focusing efforts for achieving full compatibility with other popular browsers.

Good Morning:

From our windows server logs we see the following user agents:

Safari

Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/534.57.2+(KHTML,+like+Gecko)+Version/5.1.7+Safari/534.57.2  

Firefox

Mozilla/5.0+(Windows+NT+6.1;+WOW64;+rv:22.0)+Gecko/20100101+Firefox/22.0

Chrome

Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/30.0.1599.101+Safari/537.36

IE8 with compatibility mode IE7

Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+.NET4.0C;+.NET4.0E;+InfoPath.3;+MS-RTC+EA+2;+MS-RTC+LM+8)

IE8 without compatibility mode IE7

Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+.NET4.0C;+.NET4.0E;+InfoPath.3;+MS-RTC+EA+2;+MS-RTC+LM+8)

As we were testing access to the web site using the various browsers, when looking in Dynatrace at the user visits Dashlet it did not seem to pick up the session with Firefox or Safari, is this expected? Thank you

Hi,

I took your user agents and used them with a plugin with firefox and tested them against our upcoming 5.6 release which will be available soon and is already available as early access version. All your user agents are recognized correctly (of course the IE8 in comp. mode is still resolved as IE7, because this feature is not implemented yet).

Which version are you currently using? 

Alex

Hi Alexander:

Thank you so much for your response and follow up.  Currently the main supported version of Internet Explorer for our web site is still IE8.  We expect in seeing that browser as the top browser.  This is excellent news, great to hear that the upcoming 5.6 release will be able to properly identify and capture all of those major browser user agents. This requirement has been on the top of the list for our business.  When will release 5.6 be available?  Just for my information what does an early access version entail and will it be something we could test on our test environment?  . Finally regarding having users leveraging IE8 but configured in IE7 compability mode, is there a way the Dynatrace will be able to tell us the user visit is IE7 compability mode VS a legitimate IE7 visit? Thank you!