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

How to Display the Associated Process in system.network.connections Metric with Hostmetrics Receiver on RHEL? #38520

Open
josepcorrea opened this issue Mar 11, 2025 · 4 comments
Labels

Comments

@josepcorrea
Copy link

Component(s)

receiver/hostmetrics/internal/scraper/networkscraper

Describe the issue you're reporting

Is there a way to get the system.network.connections metric to show the associated process? The receiver I'm using is hostmetrics with the network scraper, and the operating system is RHEL.

@josepcorrea josepcorrea added the needs triage New item requiring triage label Mar 11, 2025
Copy link
Contributor

Pinging code owners for receiver/hostmetrics: @dmitryax @braydonk. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

@braydonk
Copy link
Contributor

braydonk commented Mar 11, 2025

I don't think there is a way to do this with our current metric definitions. Based on a cursory reading of gopsutil I think it's possible to get this information.

When adding new metrics to the hostmetricsreceiver these days, we try to get them added to our Semantic Conventions first, and adapt them here once they are standardized there.

Please open an issue in that repo requesting a metric that counts network connections per-process and we can start the work there. I am a member of the working group for system metric semantic conventions and will prioritize that issue accordingly there. Once we have it in the semantic conventions, we can figure out a plan for implementation.

@josepcorrea
Copy link
Author

Hi @braydonk :

This is the issue: #38572

If you need anything else, let me know.

@crobert-1
Copy link
Member

Removing needs triage based on code owner's response.

@crobert-1 crobert-1 added enhancement New feature or request and removed needs triage New item requiring triage labels Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants