search

microsoft / ApplicationInsights-Announcements

Subscribe to this repo to be notified about major changes in Application Insights.
38 stars 13 forks source link

UserAgent, Lat/Long, and URL expansion data removed #3

Open BretGrinslade-zz opened 9 years ago

BretGrinslade-zz commented 9 years ago

We removed these fields from the data output for export and search. They are not set explicitly in the SDK. This change was pushed on approximately Oct 19th.

For Remote Dependency, Request, Client perf, Page view, Event:

urldata.protocol
urlData.QueryParameters
urlData.Port

The full URL is still available. In processing, we would parse out and keep copies of protocol, queryParameters, and port for easy of filtering. However, this was extra data and not exposed directly in the UI. This data can still be derived from the URL field or searched on.

For context (across events):

device.useragent
context.location.point.lat
context.location.point.long

User agent is still used for determining browser and browser version. It is dropped in processing and not available in search or export. lat / long data is no longer generated in processing. It was not very accurate and had high cardinality. For scenarios such as map visualization in Power BI, it is recommended to use country/region instead.

breyed commented 5 years ago

Should the UserAgent property be marked as obsolete? It's definition is confusing anyway:

Gets or sets the UserAgent of an application-defined account associated with the user.

It seems like it's asking for one of two distinct pieces of information: either a user's sign-in account or what browser he's using. The user's name is quite different than whether he's a fan of Edge.