![]() ![]() OpenTelemetry metrics can be created in two ways: Business metrics: A custom metric that is specific to the application or business, such as the number of users, revenue, etc.Throughput: The number of requests that the application is handling per second.Resource usage: Such as CPU usage, memory consumption, or disk space usage.Error rates: The number of errors that occur in the application, as well as their types.Request latencies: The time it takes for requests to be processed by the application.We can generate relevant measurements about our application, such as: Metrics are numerical values that represent measurements of our application performance or behavior over time. Therefore, this tutorial will focus on the metrics capability and show you how to create metrics inside your application using OpenTelemetry. But nowadays the metrics API has become stable, gaining more and more popularity, and could be a good alternative to other common tools (e.g. ![]() Originally OpenTelemetry was focused on tracing and a lot of tutorials have been written about the creation of traces using OpenTelemetry API. This telemetry data can be logs, traces or metrics (or any combination of those). OpenTelemetry is an open-source set of tools, APIs, and SDKs that enables you to generate telemetry data about your application. ![]() Whether you are familiar with OpenTelemetry and even know how to create traces in your Node app, or you never heard about OpenTelemetry and its capabilities, this tutorial will lead you step-by-step to create metrics by yourself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |