micrometer-metrics/micrometer
An application observability facade for the most popular observability tools. Think SLF4J, but for observability. observed · 2026-08-28
Health v2 · maintenance only
99/100
- Activity 99
- Release rhythm 98
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 0.0
- age_days: 3432
- days_rel: 13
- days_push: 7
- n_releases_24m: 55
Adoption not part of the score
4885 stars · 1135 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Micrometer is a vendor-neutral application observability facade for the JVM that provides a unified API for instrumenting code with dimensional metrics, distributed tracing, and observation data. It acts as an abstraction layer (similar to SLF4J for logging) that decouples instrumentation code from specific monitoring backends, allowing developers to switch between systems like Prometheus, Datadog, or New Relic without changing application code.
Use cases
- instrument java application metrics without vendor lock-in
- add prometheus metrics to spring boot app
- collect jvm application performance metrics
- switch monitoring backends without changing instrumentation code
- add distributed tracing to microservices
- track request latency and throughput in java services
- unified metrics tracing and logging instrumentation
- monitor spring boot microservices with micrometer
When to choose
- you are building a JVM-based application (Java, Kotlin, Scala) and need metrics or tracing
- you want to avoid vendor lock-in with a specific monitoring or APM tool
- you use Spring Boot, Micronaut, Quarkus, or Helidon and want built-in observability integration
- you need dimensional metrics with tags for drill-down analysis
- you want a single instrumentation API that produces metrics, traces, and logs together
When to avoid
- you are building a non-JVM application (Python, Go, Node.js, .NET) - use OpenTelemetry SDKs or language-native libraries instead
- you need full OpenTelemetry protocol features beyond what Micrometer Tracing exposes
- you want a complete observability platform with dashboards and alerting - Micrometer only collects and exports data, it does not visualize or alert
- you need log aggregation or log shipping - Micrometer's Observation API can enrich logs but is not a logging framework
- you are building a simple script or CLI tool where a full metrics facade adds unnecessary overhead
Facets
library · maturity stable
monitoring tracing monitoring microservices developer-tools jvm cross-platform metrics-facade vendor-neutral slf4j-for-observability dimensional-metrics distributed-tracing opentelemetry brave spring-boot-actuator jvm application-metrics observation-api timers gauges counters prometheus grafana datadog new-relic cloud-native telemetry apm performance-monitoring service-metrics latency-tracking histograms percentiles tag-based-metrics meter-registry spring-cloud-sleuth-successor observability-facade instrumentation spring
4 sources
- readme: https://github.com/micrometer-metrics/micrometer · fetched 2026-08-28 · daa0b6d0e5da
- homepage: https://micrometer.io · fetched 2026-08-29 · 9621e62641a5
- site_page: https://docs.micrometer.io/micrometer-docs-generator/reference · fetched 2026-08-29 · 027a52b85276
- site_page: https://micrometer.io/docs · fetched 2026-08-29 · 3965f9198adf
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| micrometer-metrics/micrometer | main | 99 |
For agents
markdown · JSON · MCP: product_card(name="micrometer-metrics/micrometer")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem