Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: host opentelemetry memory utilization #456

Merged
merged 2 commits into from
Feb 21, 2022

Conversation

rogercoll
Copy link
Contributor

Relevant information

This is adding the memory golden metric definition for hosts monitored by the opentelemetry collector.

Checklist

  • I've read the guidelines and understand the acceptance criteria.
  • The value of the attribute marked as identifier will be unique and valid.
  • I've confirmed that my entity type wasn't already defined. If it is I'm providing an
    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 and MemTotal fields from /proc/meminfo to compute the memory usage, while the Open Telemetry Collector relies on a sum of some already provided fields. We consider MemAvailable 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

@CLAassistant
Copy link

CLAassistant commented Feb 21, 2022

CLA assistant check
All committers have signed the CLA.

@apoloa apoloa merged commit 1ccf689 into newrelic:main Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants