using ASP.NET Core 10 Telemetry with OpenTelemetry and ELK
A page is slow, an API returns 500, or a database call fails. The user sees the symptom, but where do you start looking? A console message might tell you that something went wrong. To understand why, you need to connect that message to the request, its dependencies and the state of the process. That is the problem we'll work through with MVC_App . The solution has an ASP.NET Core application with MVC, Razor Pages and JSON APIs, a Blazor Server interface, and two console clients. We'll follow a request through the code, see how its telemetry reaches the backend, and use Kibana to investigate it. One distinction matters from the start: the MVC and Blazor applications send telemetry to ELK. The API console generates traffic for them, while the PostgreSQL console sends its own telemetry to Azure Monitor/Application Insights. Keeping those paths separate will save you from looking for data in the wrong place. Connection strings and keys in the examples are redacted. Supply your...