Area(s)
area:go
What's missing?
The deprecated runtime metrics contain the metric process.runtime.go.mem.heap_sys. This is useful for debugging, and I don't think there's currently a replacement.
I think this is analogous to /memory/classes/total:bytes, which is a component of go.memory.used, but there's no way to calculate /memory/classes/total:bytes from the result of the subtraction since neither metric is exposed individually.
Additional context: /memory/classes/total:bytes was in the Proposed initial metrics.
If my read of the docs is correct and these metrics are analogous, then I propose adding /memory/classes/total:bytes to the new runtime metrics as (e.g.) go.memory.total.
Describe the solution you'd like
New runtime metric added: go.memory.total
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Area(s)
area:go
What's missing?
The deprecated runtime metrics contain the metric
process.runtime.go.mem.heap_sys. This is useful for debugging, and I don't think there's currently a replacement.I think this is analogous to
/memory/classes/total:bytes, which is a component ofgo.memory.used, but there's no way to calculate/memory/classes/total:bytesfrom the result of the subtraction since neither metric is exposed individually.Additional context:
/memory/classes/total:byteswas in the Proposed initial metrics.If my read of the docs is correct and these metrics are analogous, then I propose adding
/memory/classes/total:bytesto the new runtime metrics as (e.g.)go.memory.total.Describe the solution you'd like
New runtime metric added:
go.memory.totalTip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.