Add system.linux.memory.available metric #257
Comments
|
Based on this comment, I think adding this Linux-only metric for Earlier in discussion on open-telemetry/opentelemetry-collector-contrib#7417 there was a concern about the user-friendliness of there being a separate metric for P.S. It does seem that a similar value is available in the Win32 API so that is the only source of potential confusion. We'll need to ensure the purpose of this metric is very clearly documented as to why it exists solely for Linux. |
|
This was discussed in the System metrics WG, and we agreed to go ahead with introducing |
|
Great! I'll prepare a PR in a week or two, after Braydon merges his #160. |
mx-psi
moved this from In Progress
to Blocked
in System Semantic Convention Working Group
|
Sorry for the spammy messages. I think this is unblocked now after #89? Or would we expect this to be under process metrics? |
|
Actually I think it is unblocked. I'm not sure why I suggested we wait until my PR is merged, I think I was mistaken. @ItsLastDay I believe you can move forward with this by adding it to the appropriate spot in the new yaml from #89. |
|
Ack, will do. |
github-project-automation
bot
moved this from In Progress
to Done
in System Semantic Convention Working Group
…ric (#27247) Implement a new metric `system.linux.memory.available`, which I defined in open-telemetry/semantic-conventions#257. **Link to tracking Issue:** #7417 **Testing:** added a check to an existing unit test. I had to refactor the test a bit: it assumed that a certain metric will be at position 0, which is not true now. **Documentation:** Added note in `metadata.yaml` --------- Co-authored-by: Curtis Robert <[email protected]>
…ric (open-telemetry#27247) Implement a new metric `system.linux.memory.available`, which I defined in open-telemetry/semantic-conventions#257. **Link to tracking Issue:** open-telemetry#7417 **Testing:** added a check to an existing unit test. I had to refactor the test a bit: it assumed that a certain metric will be at position 0, which is not true now. **Documentation:** Added note in `metadata.yaml` --------- Co-authored-by: Curtis Robert <[email protected]>
What are you trying to achieve?
Linux kernel exposes a memory metric called
available, which helps to understand how much memory is really available for the userspace apps. See open-telemetry/opentelemetry-collector-contrib#7417.This value is unique to Linux, hence the
system.linuxprefix: see open-telemetry/opentelemetry-collector-contrib#19149 (comment).What did you expect to see?
system.linux.memory.available- Gauge metric of integer type, meaning number of bytes available. No attributes.Additional context.
open-telemetry/opentelemetry-collector-contrib#7417 (comment)
cc @dmitryax @braydonk
The text was updated successfully, but these errors were encountered: