micrometer
An application observability facade for the most popular observability tools. Think SLF4J, but for observability.
Runssource: GitHubhomepageJavaApache-2.0commit 85e64cfa1c4d
Java, Apache-2.0 licensed. The project labels itself: cloud native, java, metrics, microservices, monitoring and observability.
micrometer runs. An Argusic agent installed it in 32 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
Micrometer builds and all 4682 tests pass across 39 modules; 3 pre-existing test failures remain in Dynatrace LTT percentile export, Statsd intermittent-failure timing, and Jetty12 request counting race.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 54 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- nebula.publish-verification plugin substitutes project(':micrometer-core') with external Maven Central artifact micrometer-core:1.17.0, causing NoSuchMethodError: DefaultMeterObservationHandler.builder() at test runtime20 minutes
- No Java JDK in container - JAVA_HOME not set, java command not found9 minutes
- DynatraceMeterRegistryTest.shouldTrackPercentilesWhenDynatraceSummaryInstrumentsNotUsed fails - LongTaskTimer percentile export wrong values
- StatsdMeterRegistryPublishTest.resumeSendingMetrics_whenServerIntermittentlyFails timeout
- TimedHandlerTest (jetty12) - expected 2 request count got 1
- Install time
- 32 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 5 hit, 2 fixed with no human help
- How the result was proved
- ./gradlew test --continue exited BUILD SUCCESSFUL; 4682 tests across 39 modules, 3 pre-existing failures in dynatrace/statsd/jetty12
- Model tokens used
- 302,082
- Exact commit tested
- 85e64cfa1c4d
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
### Errors Encountered | Error | Fix | Time | |---|---|---| | No JDK installed in container | Downloaded Adoptium JDK 17 from GitHub, set `JAVA_HOME` | 9 min | | `nebula.publish-verification` plugin substituted project dependencies with external Maven Central… | 3 pre-existing test failures (Dynatrace LTT percentile export bug, Statsd flaky timing, Jetty12 r… | `samples/micrometer-samples-spring-framework6` compile errors due to same dependency substitution… ### Test Results **4682 total tests, 3 failures, 0 errors** across all modules. The 3 failures are pre-existing bugs: - `DynatraceMeterRegistryTest` — LongTaskTimer percentile export reports `min=60000` instead of `mi… - `StatsdMeterRegistryPublishTest` — `resumeSendingMetrics_whenServerIntermittentlyFails` times out - `TimedHandlerTest` (Jetty12) — expected 2L request count but got 1L (race condition)
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 32 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Hit 5 errors during setup, 3 of which were not solved.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 88.00 | 0.18 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.38 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/micrometer)Questions
- Does micrometer run?
- Yes. micrometer runs. Argusic installed and launched it on a clean machine in 32 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test micrometer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 85e64cfa1c4d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test micrometer?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does micrometer take to install?
- 32 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does micrometer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing micrometer?
- 5 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for micrometer?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.