[GH-ISSUE #4044] [Feature Request] Expose proxy information as prometheus metric

gitea-mirror commented

2026-05-05 14:04:08 -06:00

Owner

Copy link

Originally created by @RobKenis on GitHub (Mar 6, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4044

Describe the feature request

Add a prometheus metric frp_server_proxy_info{name, type, client_version} with information that is also exposed in the dashboard. This way I can include the client version in the same Grafana dashboard as my other FRP statistics.

Describe alternatives you've considered

Can I create a custom plugin to expose this information?

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @RobKenis on GitHub (Mar 6, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4044 ### Describe the feature request Add a prometheus metric `frp_server_proxy_info{name, type, client_version}` with information that is also exposed in the dashboard. This way I can include the client version in the same Grafana dashboard as my other FRP statistics. ### Describe alternatives you've considered Can I create a custom plugin to expose this information? ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror added the

proposal

label 2026-05-05 14:04:08 -06:00

gitea-mirror commented

2026-05-05 14:04:09 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Mar 7, 2024):

The current implementation is not very elegant. The client_version should not actually be the metadata of the proxy. There should be a separate client/host object, and the proxy should be associated with this object.

We need to rethink the best implementation method here. We did not previously expose the client dimension object to the user, so this change may not be very simple.

@fatedier commented on GitHub (Mar 7, 2024): The current implementation is not very elegant. The client_version should not actually be the metadata of the proxy. There should be a separate client/host object, and the proxy should be associated with this object. We need to rethink the best implementation method here. We did not previously expose the client dimension object to the user, so this change may not be very simple.

No Branch/Tag specified