Request Telemetry is not flowing in App Insights from different subscription

Anshika Anand 21 Reputation points
2021-08-12T13:44:05.48+00:00

I have an application deployed on Azure App Service in subscription "S1" pointing to the application Insights "A1" in the same subscription.
We have created a new AppInsights "A2" in subscription "S2" and changed the telemetry for application code to log in "A2". Now, we can see all CustomEvents, Traces, Dependency logs are coming in A2 but the request logs are still going to A1.

Could someone please suggest how to fix this problem?

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
2,867 questions
{count} votes

Accepted answer
  1. Monalla-MSFT 12,121 Reputation points
    2021-09-03T19:33:03.68+00:00

    @Anshika Anand - Thanks for reaching out and for being patient.

    In order to record custom data in Application Insights, we must create a ‘Telemetry Initializer’ class within our application code which implements the ITelemetryInitializer interface. Whenever we find the need to log custom telemetry for our App Service, we need to start working with the Application Insights SDK; the codeless solution isn’t going to cut it anymore.

    In your case, since the request logs are going to A1 Subscription, ensure that you update the settings again to point the Application Insights to log in A2.

    Take a look at this docs for more reference : https://jonathancrozier.com/blog/recording-custom-telemetry-with-azure-application-insights

    Also take a look at this document for more FAQ references : https://learn.microsoft.com/en-us/azure/azure-monitor/app/asp-net-troubleshoot-no-data

    If the above response helps, Please feel free to "accept as answer" so it can be beneficial to the community.


0 additional answers

Sort by: Most helpful