Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blazor: Update docs on how to get useful metrics in application insights #30972

Open
Tracked by #5461
Liero opened this issue Mar 16, 2021 · 12 comments
Open
Tracked by #5461

Blazor: Update docs on how to get useful metrics in application insights #30972

Liero opened this issue Mar 16, 2021 · 12 comments
Assignees
Labels
area-blazor Includes: Blazor, Razor Components Docs This issue tracks updating documentation feature-analytics partner Partner ask Pillar: Technical Debt Priority:1 Work that is critical for the release, but we could probably ship without

Comments

@Liero
Copy link

Liero commented Mar 16, 2021

This is related mainly to Blazor Server Side, but there has been similar request for WASM as well.

I would like to get similar telemetry like in MVC, Razor Pages or WebForms.

  1. page views
  2. Blazor equivalents of server response time (e.g. how much took my click event handler)
  3. I want my Entity Framework / ADO.NET logs correlated to an operation (e.g. button click)
  4. I want to see which part of my blazor app is failing (e.g. which page fails to load, or which button click throws exception)

Those are untrivial if not impossible tasks for individual developers, but incredibly helpful for production use.

@javiercn javiercn added the area-blazor Includes: Blazor, Razor Components label Mar 16, 2021
@mkArtakMSFT
Copy link
Member

This is related to #5461

@ghost
Copy link

ghost commented Mar 16, 2021

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@mkArtakMSFT mkArtakMSFT added the enhancement This issue represents an ask for new feature or an enhancement to an existing one label Mar 16, 2021
@mkArtakMSFT mkArtakMSFT added Docs This issue tracks updating documentation and removed enhancement This issue represents an ask for new feature or an enhancement to an existing one labels Jul 20, 2021
@ghost
Copy link

ghost commented Jul 20, 2021

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@Liero
Copy link
Author

Liero commented Oct 26, 2021

Meanwhile, could anyone provide at least partial workaround, please?

I didn't even manage to get currently logged in user for all my logs using ITelemetryInitializer in my Blazor Server Side.

It is mostly null:

public class UserTelemetryInitializer : TelemetryInitializerBase
{
    public UserTelemetryInitializer(IHttpContextAccessor httpContextAccessor) : base(httpContextAccessor)
    { }

    protected override void OnInitializeTelemetry(HttpContext platformContext, RequestTelemetry requestTelemetry, ITelemetry telemetry)
    {
        telemetry.Context.User.Id =
        telemetry.Context.User.AuthenticatedUserId =
            platformContext.User.Identity?.Name ?? string.Empty;
    }
}

@ericbrunner
Copy link

@mkArtakMSFT Is there any progress fixing that issue?

@danroth27 danroth27 self-assigned this Sep 29, 2022
@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, .NET 8 Planning Oct 5, 2022
@ghost
Copy link

ghost commented Oct 5, 2022

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@karunakarbhogyari
Copy link

Is there any update on this? Is this issue of integrating Blazor server app with application insights done ?

@pvanroos
Copy link

What's the status of this? Is there a reason why this is languishing?

@ghost
Copy link

ghost commented Oct 6, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@mkArtakMSFT mkArtakMSFT added this to the .NET 9 Planning milestone Dec 12, 2023
@ghost
Copy link

ghost commented Dec 12, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@mkArtakMSFT mkArtakMSFT added the Priority:1 Work that is critical for the release, but we could probably ship without label Jan 11, 2024
@danroth27 danroth27 added the partner Partner ask label Jan 25, 2024
@danroth27
Copy link
Member

There is really a partner ask here to work with the App Insights team on better client integration: microsoft/ApplicationInsights-dotnet#2143. We need to understand if this should be based on the existing App Insights JS client, or the upcoming Open Telemetry JS client support.

@zachrybaker
Copy link

...And...any updates? All the bits are Microsoft, no? Can we pull things together now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components Docs This issue tracks updating documentation feature-analytics partner Partner ask Pillar: Technical Debt Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Development

No branches or pull requests

8 participants