erikvanoosten/metrics-scala

This system is a Scala library that provides instrumentation and metrics collection capabilities for applications, with specific support for Akka and Pekko actor frameworks. It enables developers to track performance metrics such as message counts, processing times, and exceptions through stackable traits, while also offering high-resolution histogram data and health check registration. The library supports various metric types including counters, gauges, timers, and meters, and facilitates both pull-based and push-based metric reporting.

The \metrics-pekko\ module now provides stackable actor traits for instrumenting Apache Pekko actors, including \ActorInstrumentedLifeCycle\ to automatically unregister gauges on actor restart, \ReceiveCounterActor\ to count received messages, \ReceiveTimerActor\ to time message processing, and \ReceiveExceptionMeterActor\ to meter thrown exceptions. This change introduces new functionality for Pekko rather than modifying existing behavior, and includes comprehensive tests for these new metrics capabilities.

metrics-pekko · high confidence

Users can now create Histogram and Timer metrics backed by the HdrHistogram library via the new HdrMetricBuilder class in the nl.grons.metrics4.scala package. This builder allows for high-resolution latency and distribution tracking, with an option to configure reservoirs that either accumulate state indefinitely or reset on each snapshot, providing more accurate percentile data for performance monitoring.

metrics-scala-hdr · high confidence

The metrics-akka module now includes new stackable actor traits that automatically instrument Akka actors. \ActorInstrumentedLifeCycle\ ensures gauges are unregistered before an actor restarts to prevent registry conflicts. \ReceiveCounterActor\, \ReceiveTimerActor\, and \ReceiveExceptionMeterActor\ provide stackable message handling that counts received messages, times message processing, and meters thrown exceptions, respectively. These traits allow developers to easily add metrics to actors by mixing them into actor classes, with default metric names based on the actor class and the specific metric type.

metrics-akka · high confidence

The library now supports push gauges, allowing users to explicitly set gauge values via \metrics.pushGauge\ or \metrics.pushGaugeWithTimeout\ rather than relying solely on lazy evaluation. A new \CheckedBuilder\ trait provides a \healthCheck\ method for registering health checks that accept various result types (Boolean, Try, Future, etc.), and \DefaultInstrumented\ and \FreshRegistries\ traits simplify registering metrics and health checks to shared or isolated registries.

metrics-scala/src/main · high confidence

The legacy SBT build definition file (JmxUtils.scala) has been removed from the project. This file previously configured the project to publish source artifacts alongside class files and defined specific dependencies, including a snapshot version of ScalaTest. Its removal indicates a shift away from this specific build setup, likely as part of a migration to a newer build tool or configuration structure.

project/build · high confidence

Added comprehensive unit tests for the metrics-scala library, covering the CheckedBuilder (health checks), Counter, Gauge, Histogram, Meter, Timer, and MetricName classes, as well as the InstrumentedBuilder, MetricBuilder (including push gauges), Implicits, DefaultInstrumented, and FreshRegistries traits.

metrics-scala/src/test · high confidence

The repository now includes a \.scala-steward.conf\ file that enables automatic dependency updates for Scala libraries via the Scala Steward bot.

(repo-wide) · high confidence

The build configuration has been updated to use the latest stable versions of key dependencies: Scala 3.3.7 and 2.13.18, Dropwizard metrics-core and metrics-healthchecks 4.2.38, HdrHistogram 2.2.2, Akka 2.5.31 and 2.6.20, and Apache Pekko 1.4.0. Test dependencies are also updated to ScalaTest 3.2.19, Mockito 5.21.0, and SLF4J Simple 2.0.17. The build now targets Java 11 by default and supports cross-compilation for Scala 2.11, 2.12, 2.13, and 3.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• First survey — no prior run to compare against. CAI 65.

• Code Health 100
• Architecture 100
• Maturity 53
• Readiness 67
• Security 68

• 300 commits — 284 feature/other, 16 fixes

• (root) — 183 commits
• project/build.properties — 39 commits
• project/plugins.sbt — 33 commits
• .github/workflows — 15 commits
• (repo) — 13 commits
• metrics-scala/src — 8 commits
• docs/AvailableVersions.md — 2 commits
• metrics-pekko/src — 2 commits
• docs/Actors.md — 1 commit
• docs/Testing.md — 1 commit
• metrics-akka-24/.gitignore — 1 commit
• metrics-akka-25/.gitignore — 1 commit
• metrics-scala-hdr/src — 1 commit

• fix: Fix mima checks, make sure to run them
• fix: Fix readme
• fix: Fix readme
• fix: Fixes Akka version for scala 2.x
• fix: Fixes Scala 2.11 compatibility
• fix: Fixes information about the 4.2.7 release
• fix: Fixes information about the 4.2.7 release (2)
• fix: Fixes output tasty version to 3.1
• fix: Fixes release problems and prepares for 2.4.8
• fix: Fixes release problems and prepares for 2.4.8 (2)
• fix: Fixes release problems and prepares for 2.4.8 (3)
• fix: Fixes the build status badge, updates outdated comment, removes scala 2.10 syntax
• fix: Re-applies #d5daa15f371 as changes got lost in a merge and more Scala 3 fixes
• fix: Released 4.3.3 (fixed link)
• fix: Releasing 4.3.7 (readme, fix)
• fix: Revert "Update scala3-library to 3.4.1 (#525)" (#527)
• change: 4.2.9 was released
• change: 4.3.0 was released!
• change: Add Sbt Dependency Submission (#469)
• change: Add release notes, use Java 11 where possible, update version matrix, scala 3.3
• …and 280 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

erikvanoosten/metrics-scala was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.