Merge pull request #219239 from v-jbasden/jbasden-merge-export-data-model

Merging /app/export-data-model.md into /app/export-telemetry.md

Author: ttorble

.openpublishing.redirection.azure-monitor.json

@@ -5521,6 +5521,11 @@
             "source_path_from_root": "/articles/azure-monitor/app/powershell-azure-diagnostics.md",
             "redirect_url": "/azure/azure-monitor/agents/diagnostics-extension-to-application-insights",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/export-data-model.md",
+            "redirect_url": "/azure/azure-monitor/app/export-telemetry",
+            "redirect_document_id": false
         }
     ]
 }

articles/azure-monitor/app/api-filtering-sampling.md

@@ -336,7 +336,7 @@ cfg: { // Application Insights Configuration
 </script>
 ```
 
-For a summary of the noncustom properties available on the telemetry item, see [Application Insights Export Data Model](./export-data-model.md).
+For a summary of the noncustom properties available on the telemetry item, see [Application Insights Export Data Model](./export-telemetry.md#application-insights-export-data-model).
 
 You can add as many initializers as you like. They're called in the order that they're added.
 
@@ -480,7 +480,7 @@ public void Initialize(ITelemetry telemetry)
 }
 ```
 
-#### Control the client IP address used for gelocation mappings
+#### Control the client IP address used for geolocation mappings
 
 The following sample initializer sets the client IP which will be used for geolocation mapping, instead of the client socket IP address, during telemetry ingestion.