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
The Prometheus metrics for traffic are inaccurate, such as frp_server_traffic_in / frp_server_traffic_out.
I used FRP to connect to a remote desktop for several hours. Below is the server's traffic monitoring, but these two metrics have hardly changed.
frpc Version
0.61.1
frps Version
0.61.1
System Architecture
client is windows 11/amd64, server is ubuntu 24.04/amd64
Bug Description
The Prometheus metrics for traffic are inaccurate, such as frp_server_traffic_in / frp_server_traffic_out.
I used FRP to connect to a remote desktop for several hours. Below is the server's traffic monitoring, but these two metrics have hardly changed.
frpc Version
0.61.1
frps Version
0.61.1
System Architecture
client is windows 11/amd64, server is ubuntu 24.04/amd64
Configurations
frps.toml
bindPort = 7000
enablePrometheus = true
webServer.addr = "0.0.0.0"
webServer.port = 17600
Logs
No response
Steps to reproduce
...
Affected area
The text was updated successfully, but these errors were encountered: