Turning many standard dimensions into non-segmentable attributes

Question

Turning many standard dimensions into non-segmentable attributes

vgorbenko opened this issue 9 years ago · 0 comments

After analyzing usage of standard dimensions in AppInsights, we decided to turn many of non-commonly used dimensions into plain properties. This will make it easier to find the ones that are important (instead of scrolling through long lists), will increase performance of AppInsights UI, and, of course, will reduce our cost of storing data that only very few people need. Below you can find a list of dimensions that will stay, will be removed, and some FAQs about the planned change.

Here is the current consolidated list of dimensions that are staying:

```
       availability.result  
```
```
       availability.runLocation  
```
```
       availability.testName 
```
```
       basicException.problemId
```
```
       billingMetric.documentType
```

       clientPerformance.performanceBucket

```
       context.data.isSynthetic
```
```
       context.device.browserVersion
```
```
       context.device.deviceModel
```
```
     context.device.osVersion
```
```
     context.device.roleInstance
```
```
     context.device.type
```
```
     context.location.country
```
```
     context.operation.name
```
```
     event.name
```
```
     remoteDependency.baseName
```

     remoteDependency.durationMetric.name

     remoteDependency.performanceBucket

```
     remoteDependency.resultCode
```
```
     remoteDependency.success
```
```
     request.performanceBucket
```
```
     request.responseCode
```
```
     request.success
```
```
     view.name  
```
```
     view.performanceBucket
```
```
     context.device.deviceName
```

     context.device.screenResolution.value

```
     view.name
```
```
     context.application.version
```
```
     Context.sessionid
```
```
     Context.anonuserid
```
```
     Insight.severity
```
```
     Insight.provider
```

Dimensions that are being turned into non-segmentable attributes:

• basicException.assembly
• basicException.exceptionGroup
• basicException.exceptionType
• basicException.failedUserCodeAssembly
• basicException.failedUserCodeMethod
• basicException.handledAt
• basicException.hasFullStack
• basicException.innermostExceptionThrownAtAssembly
• basicException.innermostExceptionThrownAtMethod
• basicException.innermostExceptionType
• basicException.method
• basicException.outerExceptionThrownAtAssembly
• basicException.outerExceptionThrownAtMethod
• basicException.outerExceptionType
• basicException.parsedStack.assembly
• basicException.parsedStack.fileName
• basicException.parsedStack.method
• basicException.severityLevel
• basicException.typeName
• clientPerformance.urlData.base
• context.application.build
• context.cloud.deploymentUnit
• context.cloud.environment
• context.cloud.location
• context.cloud.name
• context.cloud.role
• context.cloud.roleInstance
• context.device.language
• context.device.locale
• context.device.network
• context.device.oemName
• context.device.os
• context.device.screenResolution.height
• context.device.screenResolution.width
• context.device.vmName
• context.location.continent
• context.serverDevice.os
• context.serverDevice.osVersion
• context.user.campaignId
• context.user.storeRegion
• event.type
• event.urlData.base
• event.urlData.host
• event.urlData.protocol
• event.urlData.raw
• message.hasStackTrace
• message.level
• message.severity
• message.severityLevel
• performanceCounter.categoryName
• performanceCounter.instanceName
• remoteDependency.async
• remoteDependency.commandName
• remoteDependency.dependencyTypeName
• remoteDependency.type
• request.httpMethod
• request.urlData.base
• request.urlData.host
• request.urlData.protocol
• view.referrerData.base
• view.urlData.base
• view.urlData.host
• view.urlData.port
• view.urlData.protocol

# These are the FAQs about the change:

Q: Will SDK continue to collect the values for the dimensions that are being cut?
A: There are no plan on changing AI SDK side. All data will remain available at:
• Event details screen
• Continuous export

*Q: If all data continues to float to AI, what areas are really impacted by the cut? *
A: The users will not be able to use the affected dimensions in the Metrics Explorer “group-by” drop-down box. Also, these dimensions will no longer be available in the filter list (in ME and Diagnostic Search).

*Q: Will I continue to be able to group-by/ filter by custom dimensions? *
A: Yes, absolutely. Custom dimensions will continue to work the way they work today.