Conversation
solnic
added this pull request to stack #1214
September 16, 2026 13:34
solnic
marked this pull request as draft
September 16, 2026 13:37
solnic
force-pushed
the
feat/runtime-metrics-system-limits
branch
2 times, most recently
from
September 16, 2026 14:05
ef9846f to
e6f463b
Compare
solnic
force-pushed
the
feat/runtime-metrics-system-limits
branch
from
September 17, 2026 09:50
e6f463b to
6f43e76
Compare
solnic
force-pushed
the
feat/runtime-metrics-system-limits
branch
from
September 17, 2026 10:00
6f43e76 to
3a69aec
Compare
solnic
force-pushed
the
feat/runtime-metrics-system-limits
branch
2 times, most recently
from
September 17, 2026 11:27
5ca9339 to
16bbdbd
Compare
solnic
force-pushed
the
feat/runtime-metrics-system-limits
branch
2 times, most recently
from
September 17, 2026 13:14
7456663 to
1f9f7d8
Compare
solnic
marked this pull request as ready for review
September 17, 2026 13:15
solnic
force-pushed
the
feat/runtime-metrics-system-limits
branch
from
September 18, 2026 07:16
1f9f7d8 to
be77a8c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the VM's resource counters and how close they are to their hard limits, as gauges:
elixir.runtime.process.count/.limit/.utilizationelixir.runtime.atom.count/.limit/.utilizationelixir.runtime.port.count/.limit/.utilizationutilizationis the ratio between the count and the limit. These are the three limits that take a node down hard when they are reached - hittingprocess_limitorport_limitmeans no more work can start, and the atom table is never garbage collected, soatom.utilizationcreeping up is a leak you want an alert on well before it becomes an outage.Everything comes out of the
[:vm, :system_counts]measurement map that telemetry_poller already emits.Older telemetry_poller versions
The
*_limitkeys were only added to that event in telemetry_poller 1.3.0, and the SDK allows~> 1.0so that apps pinned to an older one still resolve. When the limits are absent, the.countgauges are still reported and.limit/.utilizationare quietly skipped.