Metrics You Get Without Writing Any
67 records in the metrics snapshot. The service wrote 6 of them. 👋 I'm Anton - a software engineer working mostly in PHP/Symfony and Go, currently carving a live PHP monolith into Go services. Part 1 of this series was about the manifest as the single declaration a service makes about itself; Part 2 was about the environment-variable catalog that falls out of it. This part is the same question…
This article discusses the metrics that can be automatically generated by a service without any additional instrumentation code. The service in question, developed by software engineer Anton, exposes 67 metrics by default, nine out of ten of which are generated by the platform library it imports. These metrics are emitted by the platform and wired up based on the service's manifest declarations.
Among the automatically generated metrics, the service provides information about its liveness and readiness, build version, gRPC request counts, broker driver metrics, outbound relay metrics, Postgres pool metrics, and Go runtime metrics. All of these metrics are emitted by the platform library and do not require any additional code in the service itself. This allows for the observability of various aspects of the service without the need for manual instrumentation efforts.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
