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

Ensure that we have good set of telemetry data from Entity Framework #225

Open
2 tasks
SandGrainOne opened this issue Oct 17, 2024 · 0 comments
Open
2 tasks
Labels
kind/user-story Used for issues that describes functionality for our users.

Comments

@SandGrainOne
Copy link
Member

SandGrainOne commented Oct 17, 2024

Description

We need to ensure that we get telemetry data out of Entity Framework. Investigate what we get out of the box and turn on Telemetry if not already enabled. This issue is focusing on enabling OTel. We can discuss specific counters and metrics in later meetings.

One example would be the ability to see what SQL statements that is being run as part of the trace of a request.

Additional Information

Can be testet locally in dev by targeting an Application Insights instance in AT, eg: AT22.

https://learn.microsoft.com/en-us/ef/core/logging-events-diagnostics/metrics?tabs=windows#metrics

Tasks

  • Make sure Entity Framework registeres telemetry data that we can trace in Application Insight

Acceptance Criterias

  • Profile has logging (writing) of telemetry data from Entity Framework that we can analyze in Application Insights.
@SandGrainOne SandGrainOne added the status/draft Status: When you create an issue before you have enough info to properly describe the issue. label Oct 17, 2024
@SandGrainOne SandGrainOne added kind/user-story Used for issues that describes functionality for our users. and removed status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story Used for issues that describes functionality for our users.
Projects
None yet
Development

No branches or pull requests

1 participant