Area(s)
area:go
What's missing?
The deprecated runtime metrics have the following useful GC metrics:
process.runtime.go.gc.count
process.runtime.go.gc.pause_ns
The GC count is often useful for debugging memory issues in code, and I think this should be added to the new runtime metrics as (e.g.) go.memory.gc.count.
Having a pause time histogram is useful as well. I see discussion in the original ticket for the new runtime metrics that suggests this one in particular can be a poor signal: golang/go#67120 (comment)
However, it seems that there was never a recommend metrics for pauses made (at least none that I see in the current list), so I suggest adding this value to the new runtime metrics as (e.g.) go.memory.gc.pause.duration.
Describe the solution you'd like
New runtime metrics added:
go.memory.gc.count
go.memory.gc.pause.duration
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 have the following useful GC metrics:
process.runtime.go.gc.countprocess.runtime.go.gc.pause_nsThe GC count is often useful for debugging memory issues in code, and I think this should be added to the new runtime metrics as (e.g.)
go.memory.gc.count.Having a pause time histogram is useful as well. I see discussion in the original ticket for the new runtime metrics that suggests this one in particular can be a poor signal: golang/go#67120 (comment)
However, it seems that there was never a recommend metrics for pauses made (at least none that I see in the current list), so I suggest adding this value to the new runtime metrics as (e.g.)
go.memory.gc.pause.duration.Describe the solution you'd like
New runtime metrics added:
go.memory.gc.countgo.memory.gc.pause.durationTip
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.