[GH-ISSUE #3249] [Feature Request] 关于Dashboard统计数据的建议

gitea-mirror commented

2026-05-05 13:40:51 -06:00

Owner

Copy link

Originally created by @NoDeadCarp on GitHub (Jan 10, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3249

Describe the feature request

目前Dashboard的统计数据是直接存储在内存中，并没有存储在磁盘
每次重启frps后统计数据会清零
建议作者考虑存储在磁盘中，并提供可修改的保存数据的时间，使其重启后统计数据从重启前的数据继续统计，方便用户看见整体数据
此issue在2016年已经被提过了，目前已经被关闭，但是我身边有很多使用frp的用户都有这个需求，希望作者能再次考虑一下
感谢

Describe alternatives you've considered

No response

Affected area

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

Originally created by @NoDeadCarp on GitHub (Jan 10, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3249 ### Describe the feature request 目前Dashboard的统计数据是直接存储在内存中，并没有存储在磁盘每次重启frps后统计数据会清零建议作者考虑存储在磁盘中，并提供可修改的保存数据的时间，使其重启后统计数据从重启前的数据继续统计，方便用户看见整体数据此issue在2016年已经被提过了，目前已经被关闭，但是我身边有很多使用frp的用户都有这个需求，希望作者能再次考虑一下感谢 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror

2026-05-05 13:40:51 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:40:54 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Jan 15, 2023):

持久化需求建议使用 prometheus 采集。

https://github.com/fatedier/frp/blob/dev/conf/frps_full.ini#L60

@fatedier commented on GitHub (Jan 15, 2023): 持久化需求建议使用 prometheus 采集。 https://github.com/fatedier/frp/blob/dev/conf/frps_full.ini#L60

gitea-mirror commented

2026-05-05 13:40:55 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Feb 15, 2023):

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

@github-actions[bot] commented on GitHub (Feb 15, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified