Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jabrena/182-java-observability-metrics-micrometer
Use when you need to implement or improve Java metrics observability with Micrometer — including meter design, naming/tag conventions, cardinality control, timers/counters/gauges/distribution summaries, percentiles/histograms, Actuator/Prometheus integration, and metrics validation through tests. This should trigger for requests such as Improve metrics; Apply Micrometer; Add metrics observability; Refactor Micrometer instrumentation; Add Micrometer timers counters or gauges to Java services. Par
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We have an asynchronous queue worker handling background tasks in Java, and we want to monitor execution latency, processed item counts, and current queue depth using Micrometer. Please draft the instrumented Java service class along with the verification command to validate the build and test suite.
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies running clean verify with Maven. | Missed | Passed |
| The response instruments queue depth using a Gauge. | Passed | Passed |
| The response instruments item processing counts using a Counter. | Passed | Passed |
The instructions your model reads when the skill loads.
Implement effective Java metrics instrumentation with Micrometer by defining meaningful service-level metrics, controlling cardinality, selecting the right meter type, and exposing production-ready telemetry for dashboards and alerting.
What is covered in this Skill?
Scope: Application-level metrics design and instrumentation quality for Java services, with emphasis on operationally useful and cost-efficient telemetry.
Metrics instrumentation must be operationally safe, low-cardinality, and validated. Poor tag design or excessive meter creation can degrade observability systems and increase costs.
./mvnw clean verify or mvn clean verify after changesIdentify key service indicators (throughput, latency, error ratio, saturation) and map each to stable metric names, units, and low-cardinality tags.
test cases passed, vs 21 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.