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

关于大流量下MetricNode过多求教：可否降低日志落盘频率 #1843

Closed
renxinlin opened this issue Nov 5, 2020 · 2 comments
Closed

关于大流量下MetricNode过多求教：可否降低日志落盘频率 #1843

renxinlin opened this issue Nov 5, 2020 · 2 comments
Labels
area/logging Issues or PRs related to logging of Sentinel area/metrics Issues or PRs related to metrics and monitoring area/performance Issues or PRs related to runtime performance

Comments

@renxinlin
Copy link

renxinlin commented Nov 5, 2020 •
edited
Loading

SCHEDULER.scheduleAtFixedRate(new MetricTimerListener(), 0, 1, TimeUnit.SECONDS);
这里定时器的时间能否配置化;降低下执行频率

List nodesOfEverySecond = rollingCounterInMinute.details();
// 未使用
rollingCounterInMinute.detailsOnCondition(timePredicate);
这里的timePredicate是指窗口开始时间吗？ 能否弄成配置化

执行器的频率如果小于窗口的时间,收集度量信息到磁盘的效果与现在的是否相同？
@sczyh30 sczyh30 added the area/performance Issues or PRs related to runtime performance label Nov 16, 2020
@brotherlu-xcq
Copy link
Collaborator

the same question: #1867

@sczyh30 sczyh30 changed the title 关于大流量下MetricNode过多求教 关于大流量下MetricNode过多求教：可否降低日志落盘频率 Apr 13, 2021
@sczyh30 sczyh30 added area/logging Issues or PRs related to logging of Sentinel area/metrics Issues or PRs related to metrics and monitoring labels Apr 13, 2021
@sczyh30
Copy link
Member

sczyh30 commented Apr 13, 2021

Resolved via #1919 (released in 1.8.1)

@sczyh30 sczyh30 closed this as completed Apr 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/logging Issues or PRs related to logging of Sentinel area/metrics Issues or PRs related to metrics and monitoring area/performance Issues or PRs related to runtime performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sczyh30 @brotherlu-xcq @renxinlin