Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The Prometheus metrics for traffic are inaccurate. #4651

Closed
1 of 11 tasks
BQsummer opened this issue Jan 28, 2025 · 1 comment
Closed
1 of 11 tasks

The Prometheus metrics for traffic are inaccurate. #4651

BQsummer opened this issue Jan 28, 2025 · 1 comment

Comments

@BQsummer
Copy link

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.

Image

Image

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

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
@fatedier
Copy link
Owner

fatedier commented Feb 7, 2025

Currently, traffic on this connection is only counted when the connection is closed.

@BQsummer BQsummer closed this as completed Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fatedier @BQsummer