Azure Application Insights Telemetry Data Model Telemetry Context Azure Monitor

From Marvel vs DC
Revision as of 13:40, 26 January 2021 by Sandrayogurt3 (talk | contribs) (Created page with "<span style="display:block;text-align:center;clear:both"></span><br /><p>Every telemetry item may have a strongly typed context fields. Every field enables a specific monitori...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Every telemetry item may have a strongly typed context fields. Every field enables a specific monitoring scenario. Use the custom properties collection to store custom or application-specific contextual information. Information in the application context fields is always about the application that is sending the telemetry. Application version is used to analyze trend changes in the application behavior and its correlation to the deployments. The IP address of the client device. IPv4 and IPv6 are supported. When telemetry is sent from a service, the location context is about the user that initiated the operation in the service. Application Insights extract the geo-location information from the client IP and then truncate it. So client IP by itself cannot be used as end-user identifiable information. Originally this field was used to indicate the type of the device the end user of the application is using. Today used primarily to distinguish JavaScript telemetry with the device type 'Browser' from server-side telemetry with the device type 'PC'. A unique identifier of the root operation. This identifier allows to group telemetry across multiple components. See telemetry correlation for details. The operation id is created by either a request or a page view. All other telemetry sets this field to the value for the containing request or page view. The unique identifier of the telemetry item's immediate parent. See telemetry correlation for details. The name (group) of the operation. The operation name is created by either a request or a page view. All other telemetry items set this field to the value for the containing request or page view. Operation name is used for finding all the telemetry items for a group of operations (for example 'GET Home/Index'). Name of synthetic source. Some telemetry from the application may represent synthetic traffic. It may be web crawler indexing the web site, site availability tests, or traces from diagnostic libraries like Application Insights SDK itself. Session ID - the instance of the user's interaction with the app. Information in the session context fields is always about the end user. When telemetry is sent from a service, the session context is about the user that initiated the operation in the service. Anonymous user id. Represents the end user of the application. When telemetry is sent from a service, the user context is about the user that initiated the operation in the service . Sampling is one of the techniques to minimize the amount of collected telemetry. Sampling algorithm attempts to either sample in or out all the correlated telemetry. Anonymous user id is used for sampling score generation. So anonymous user id should be a random enough value. Using contextual backlink id to store user name is a misuse of the field. Use Authenticated user id. Authenticated user id. The opposite of anonymous user id, this field represents the user with a friendly name. In multi-tenant applications this is the account ID or name, which the user is acting with. Examples may be subscription ID for Azure portal or blog name for a blogging platform. Name of the role the application is a part of. Maps directly to the role name in azure. Can also be used to distinguish micro services, which are part of a single application. Name of the instance where the application is running. Computer name for on-premises, instance name for Azure. SDK version. See this article for information. This field represents the node name used for billing purposes. Use it to override the standard detection of nodes. Learn how to extend and filter telemetry. See data model for Application Insights types and data model. Check out standard context properties collection configuration.