beam-telemetry/telemetry_poller

This system is a telemetry polling library that periodically gathers and publishes VM-level metrics as Telemetry events. It provides built-in measurements for memory usage, run queue lengths, system counts, and process information. The project has been fully rewritten in Erlang, replacing its previous Elixir implementation and legacy configuration mechanisms.

New example modules (TelemetryPollerVM in Elixir and Erlang) demonstrate how to attach telemetry handlers for VM-level metrics. These examples show how to capture and display measurements for memory usage, total run queue lengths, and system counts (including atom, port, and process limits), providing reference implementations for monitoring these specific VM statistics.

examples · high confidence

The Telemetry.Sampler module, which previously allowed users to periodically gather measurements and publish them as Telemetry events, has been removed from the library.

lib · high confidence

The library has been converted from Elixir to Erlang, changing the module access from \Telemetry.Poller\ to \telemetry\_poller\. The configuration API has changed: the previous \vm\_measurements\ and \measurements\ keys are now unified into a single \measurements\ key. Several specific VM memory measurements (e.g., \:total\_memory\, \:atom\_memory\) were removed in favor of a single \:memory\ measurement that returns all values from \erlang:memory/0\. New measurements include \:process\_info\ and \:system\_counts\ (which reports process, atom, and port counts and limits). The library now requires Erlang/OTP 24+ and Telemetry \~\> 1.0.

(repo-wide) · high confidence

The \config/config.exs\ file, which previously utilized the deprecated \Mix.Config\ module, has been removed from the project. This change eliminates the legacy configuration mechanism, likely as part of a migration to a newer configuration system or to clean up obsolete files.

config · high confidence

The telemetry\_poller library has been converted from Elixir to Erlang, introducing a new Erlang API (telemetry\_poller:start\_link/1) alongside the existing Elixir interface. This release adds built-in support for measuring persistent\_term and system\_counts (including atom, port, and process limits) alongside the existing memory and run queue metrics. The default poller is now configurable via the application environment and can be disabled by setting the 'default' key to false.

src · high confidence

The project has migrated its test suite from Elixir/ExUnit to Erlang/Common Test. This change adds a comprehensive Common Test suite (\telemetry\_poller\_SUITE.erl\) that validates the \telemetry\_poller\ application's behavior, including configuration options (name, global name, period, init\_delay), error handling for invalid inputs, listing measurements, and the dispatching of specific built-in measurements like \memory\, \persistent\_term\, \system\_counts\, \total\_run\_queue\_lengths\, and \process\_info\. It also introduces support modules (\test\_handler.erl\ and \test\_measure.erl\) to facilitate these tests. Concurrently, legacy Elixir test files (\telemetry\_sampler\_test.exs\ and \test\_helper.exs\) have been removed.

test · high confidence

The project's Elixir build configuration has been removed, specifically the \mix.exs\ file and the \mix.lock\ lockfile. This eliminates the dependency on the \telemetry\ library (version 0.1.0) and the Elixir runtime requirements defined in the previous project structure.

(dependencies) · high confidence

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

• CAI 59 → 60 (+0.3)
• Rubric changed (rubric-2026.09.12 → rubric-2026.09.18) — scores are not directly comparable.

• Code Health 100 → 100 (+0.0)
• Architecture 69 → 69 (+0.0)
• Maturity 38 → 38 (+0.0)
• Readiness 78 → 80 (+2.2)
• Security 100 → 100 (+0.0)

• Coverage not measured — no coverage collector is wired up
• Documentation: no usage examples (README.md)

• Outdated: telemetry

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

beam-telemetry/telemetry_poller 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.