How can we improve Application Insights?

Capture Region of Executing Process as part of analytics data

In the analytics schema, we have fields cloud_RoleName and cloud_RoleInstance. When an application is deployed to multiple regions and each deployment is using a single instrumentation key, it would be useful to split data by the cloud geographic region that processed the telemetry,

e.g. cloud_GeoRegion, to contain data such as 'West Europe', 'West US', 'UK West' etc.

This would apply to any of the schemas, where cloud_RoleName and cloud_RoleInstance are recorded.

5 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dylan Morley shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    Sergey might be able to help you find ways to do this on your own. But we don’t have any plans to do this automatically in the App Insights SDK, given the breadth and telemetry size consequences of that kind of change.

    - David from the App Insights team

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Dylan Morley commented  ·   ·  Flag as inappropriate

        @Sergey - we're just going to build this in to our app configuration, so we can enrich telemetry with the setting.

      • Dylan Morley commented  ·   ·  Flag as inappropriate

        Hey @Sergey, a couple of use cases as follows. In both cases, consider the process to be deployed to EUW and EUN, both sending to a single instrumentation key.

        1) A web api processing client requests. We would like to enrich the request telemetry to include the region of the web API that received and processed the request

        2) A Daemon app of some variety, generating customEvents / metrics / exceptions etc. We would also like to enrich this telemetry with the geo-region that generated the telemetry

        With the cross-instrumentation key enhancements that have been introduced recently, we're moving more towards a 1-2-1 relationship between an application deployed to a region and an instrumentation key for the application in that region, which then gives us this capability.

        However, we have a number of apps not in this state at the moment and it would be useful to know if we can easily enrich the telemetry with this information, allowing us to easily split and graph data accordingly.

      • Sergey Kanzhelev commented  ·   ·  Flag as inappropriate

        So you need to get region as part of every event? Do you need the region that produced the telemetry or region of endpoint received it?

      Feedback and Knowledge Base