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.

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

Increase servers statistics frequency to once per1H #25870

Closed
sharon-fdm opened this issue Jan 29, 2025 · 3 comments
Closed

Increase servers statistics frequency to once per1H #25870

sharon-fdm opened this issue Jan 29, 2025 · 3 comments
Labels
~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. #g-orchestration Orchestration product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. story A user story defining an entire feature
Milestone

Comments

@sharon-fdm
Copy link
Collaborator

sharon-fdm commented Jan 29, 2025

Goal

User story
As a developer,
I want to see statistics from servers coming once per hour
so that I can have quicker feedback to changes.

Key result

Servers starting from 4.64.0 will report statistics every 1 hour.

@sharon-fdm sharon-fdm added #g-orchestration Orchestration product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. story A user story defining an entire feature ~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. labels Jan 29, 2025
@sharon-fdm
Copy link
Collaborator Author

sharon-fdm commented Jan 29, 2025

@xpkoala , there is nothing for you to QA now so moving directly to "Ready for release".
This will only take effect when we release 4.64.0

@sharon-fdm sharon-fdm added this to the 4.64.0-tentative milestone Jan 29, 2025
@sharon-fdm
Copy link
Collaborator Author

FYI (no action required)
@zayhanlon, @noahtalerman, this will be part of 4.64.0

@fleet-release
Copy link
Contributor

Hourly stats stream,
Like a river's steady flow,
Guidance for coders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. #g-orchestration Orchestration product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. story A user story defining an entire feature
Projects
None yet
Development

No branches or pull requests

2 participants