-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
add proxy name label to the proxy_count prometheus metric #4985
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
Conversation
… break existing queries
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a more detailed Prometheus metric for proxy counting that includes the proxy name as a label. This enables monitoring of individual proxy connections rather than just aggregate counts by type.
- Introduces a new
proxy_counts_detailedmetric with both proxy type and name labels - Updates the
NewProxyandCloseProxymethods to track individual proxy instances - Registers the new metric with the Prometheus registry
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <[email protected]>
* commit 'ee3cc4b14ea2f8c9581fa06b7151593b94f4ddcc': Fix CloseNotifyConn.Close function (fatedier#5022) update README (fatedier#5001) bump version to v0.65.0 and update release notes (fatedier#4998) update sponsors info (fatedier#4997) chore: fix struct field name in comment (fatedier#4993) auth: enhance OIDC client with TLS and proxy configuration options (fatedier#4990) add proxy name label to the proxy_count prometheus metric (fatedier#4985) update go version to 1.24 (fatedier#4960) update README (fatedier#4957) improve yamux logging (fatedier#4952) xtcp: add configuration to disable assisted addresses in NAT traversal (fatedier#4951) remove quotes (fatedier#4938) Merge pull request fatedier#4928 from fatedier/xtcp
WHY
In my use case, I have many different frpc binaries connecting to the same frps binary. Each frpc binary has a unique proxy name configured.
For this reason, it is useful to know which proxy (i.e. worker/control connection) is active. Without this PR, I can only know how many proxies are connected, but not which ones.
Fix #4986