[GH-ISSUE #5089] [Feature Request] Get traffic metrics via httpPlugins ops callback

gitea-mirror commented

2026-05-05 14:32:23 -06:00

Owner

Copy link

Originally created by @gregoiregentil on GitHub (Dec 9, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5089

Describe the feature request

THank you (again) for this great project.

I'm aware of enablePromotheus (which I have enabled) and I would like to get traffic usage, aka. transferred byte amount via:
httpPlugins
ops = ["CloseProxy"]

The promotheus interface does show:
frp_server_traffic_in{name="myname",type="tcp"} 2055
so the information is "there"

Have I missed an option or a meta that would already exist to get such traffic info in httpPplugins for that specific proxy?

Otherwise, could it be implemented? Or could I get some guidance how to patch?

Describe alternatives you've considered

No alternatives known.

Affected area

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

Originally created by @gregoiregentil on GitHub (Dec 9, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5089 ### Describe the feature request THank you (again) for this great project. I'm aware of enablePromotheus (which I have enabled) and I would like to get traffic usage, aka. transferred byte amount via: [[httpPlugins]] ops = ["CloseProxy"] The promotheus interface does show: frp_server_traffic_in{name="myname",type="tcp"} 2055 so the information is "there" Have I missed an option or a meta that would already exist to get such traffic info in httpPplugins for that specific proxy? Otherwise, could it be implemented? Or could I get some guidance how to patch? ### Describe alternatives you've considered No alternatives known. ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [x] Server Plugin - [x] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:32:23 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:32:26 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Dec 9, 2025):

Currently we do not have plans to expose statistics at the plugin layer. Plugins are mainly intended for extending control-plane functionality rather than for exposing metrics.

@fatedier commented on GitHub (Dec 9, 2025): Currently we do not have plans to expose statistics at the plugin layer. Plugins are mainly intended for extending control-plane functionality rather than for exposing metrics.

gitea-mirror commented

2026-05-05 14:32:26 -06:00

Author

Owner

Copy link

@gregoiregentil commented on GitHub (Dec 9, 2025):

Can you guide how and where to patch? Is it complicated or is it just adding some "pipes"? Because calculation and data already exist...

@gregoiregentil commented on GitHub (Dec 9, 2025): Can you guide how and where to patch? Is it complicated or is it just adding some "pipes"? Because calculation and data already exist...

gitea-mirror commented

2026-05-05 14:32:27 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Dec 9, 2025):

If you want to modify the code yourself, it should be relatively easy now with the help of AI tools.

@fatedier commented on GitHub (Dec 9, 2025): If you want to modify the code yourself, it should be relatively easy now with the help of AI tools.

gitea-mirror commented

2026-05-05 14:32:28 -06:00

Author

Owner

Copy link

@gregoiregentil commented on GitHub (Dec 9, 2025):

Great answer! We are just wasting keystrokes...

@gregoiregentil commented on GitHub (Dec 9, 2025): Great answer! We are just wasting keystrokes...

gitea-mirror commented

2026-05-05 14:32:29 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Dec 24, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Dec 24, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:32:29 -06:00

Author

Owner

Copy link

@gregoiregentil commented on GitHub (Dec 24, 2025):

The proposed pull-request has been successfully tested.

@gregoiregentil commented on GitHub (Dec 24, 2025): The proposed pull-request has been successfully tested.

gitea-mirror commented

2026-05-05 14:32:30 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Dec 24, 2025):

Currently we do not have plans to expose statistics at the plugin layer. Plugins are mainly intended for extending control-plane functionality rather than for exposing metrics.

@fatedier commented on GitHub (Dec 24, 2025): > Currently we do not have plans to expose statistics at the plugin layer. Plugins are mainly intended for extending control-plane functionality rather than for exposing metrics.

gitea-mirror commented

2026-05-05 14:32:31 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 8, 2026):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jan 8, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified