Tracking Application Health With OpenTelemetry Metrics in .NET
HTML-код
- Опубликовано: 18 окт 2024
- ►► Master Web API development Best Practices: bit.ly/3TnqoFQ
►► Build great web apps in Blazor WebAssembly: bit.ly/437g87T
►► Support us on Patreon and get the source code: / codemaze
Hello everyone. My name is Marinko Spasojevic and in this video, I will show you how to use OpenTelemetry metrics to gain insight into the health and performance and even issues our applications may be experiencing.
Metrics are one of the 3 fundamental pillars of OpenTelemetry, and they represent an aggregation of numeric data over time, providing measurements for our applications.
As I already said, a metric is a measurement of a service or application that we capture at runtime, and aggregate over a given time period. These metrics provide insight into our applications' availability, health, and performance.
The OpenTelemetry project provides a set of client libraries for .NET that allows us to collect metrics on measurements such as HTTP requests/responses, and memory allocation.
LINKS MENTIONED IN THE VIDEO
►► Logging With Open Telemetry - • Logging With OpenTelem...
FOLLOW US ON SOCIAL MEDIA!
►► / marinko-spasojevic
►► / codemazeblog
►► / codemazeblog
Thank you all for watching and for your support.
►► If you want to master Web API development using best practices, check out our Web API book: bit.ly/3x75ZMM
►► Also, to build great full-stack apps with Blazor, check out our course: bit.ly/3Pw3Y33
Thanks
Welcome. Thank you for watching the video
Thanks 🎉
You're welcome 😊
what's the best way to run Prometheus in production, I have the opensource exe on a dedicated server but keeps shutting down after a period of time
Hmmm... the best way... I can't tell, there are situations for different approaches for sure. I was talking to my team and we always ran it through Docker, generally in a Kubernetes cluster. That way it is resilient to restarts (handled by Kubernetes) and means we can have multiple instances should it be required.