You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We would like to request a new metric to count the number of network connections per process. Currently, the hostmetricsreceiver does not provide this information, and there doesn't seem to be an existing metric that gives a per-process count of network connections.
Describe the solution you'd like
Being able to track the number of network connections per process would be useful for monitoring and troubleshooting scenarios, such as identifying processes with a high number of open network connections or detecting potential connection leaks.
Describe alternatives you've considered
Please consider adding a metric that counts the number of network connections per process to the system metric semantic conventions. Once the metric is added and standardized, we can plan for its implementation in the hostmetricsreceiver and OpenTelemetry.
As a member of the working group for system metric semantic conventions, I will prioritize this issue in the group once it's created.
Additional context
This issue follows the guidelines for introducing new metrics and emphasizes the importance of standardizing the metric within the Semantic Conventions first, which aligns with the process you mentioned.
The text was updated successfully, but these errors were encountered:
Component(s)
No response
Is your feature request related to a problem? Please describe.
We would like to request a new metric to count the number of network connections per process. Currently, the hostmetricsreceiver does not provide this information, and there doesn't seem to be an existing metric that gives a per-process count of network connections.
Describe the solution you'd like
Being able to track the number of network connections per process would be useful for monitoring and troubleshooting scenarios, such as identifying processes with a high number of open network connections or detecting potential connection leaks.
Describe alternatives you've considered
Please consider adding a metric that counts the number of network connections per process to the system metric semantic conventions. Once the metric is added and standardized, we can plan for its implementation in the hostmetricsreceiver and OpenTelemetry.
As a member of the working group for system metric semantic conventions, I will prioritize this issue in the group once it's created.
Additional context
This issue follows the guidelines for introducing new metrics and emphasizes the importance of standardizing the metric within the Semantic Conventions first, which aligns with the process you mentioned.
The text was updated successfully, but these errors were encountered: