feat: host opentelemetry memory utilization #456
Merged
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.
Relevant information
This is adding the memory golden metric definition for hosts monitored by the opentelemetry collector.
Checklist
identifier
will be unique and valid.explanation above.
Comments
In Linux systems, the resulting value will be different than the one provided by the infra-agent host. The agent uses the
MemAvailable
andMemTotal
fields from/proc/meminfo
to compute the memory usage, while the Open Telemetry Collector relies on a sum of some already provided fields. We considerMemAvailable
more fine-grained as it is computed in the kernel and it takes into account memory low watermarks.Issue proposing
MemAvailable
as a new state for the Open Telemetry Collector: open-telemetry/opentelemetry-collector-contrib#7417