-
Notifications
You must be signed in to change notification settings - Fork 440
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
feat: log how long tenant activation takes #4080
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to the comments, I think we should have a global histogram metric for the timing as well, so we can start treating tenant activation time as a (soft) pageserver SLO and alert on it.
Would love to see the metric added in this PR as well, with the observe() call right next to the info!()
line you added.
Test results for 3efeccb:debug build: 219 tests run: 209 passed, 0 failed, 10 (full report)release build: 219 tests run: 209 passed, 0 failed, 10 (full report) |
I was hoping to get this in for the release since we have been sitting on the user-visible problem for offsite + week. I want to have something to make progress on the user-visible issue, you can follow-up with the metric for the next release. |
Ok, will create an issue for the metric. |
instead of using Debug impl which includes a full backtrace pointing to few lines above, let's use the naming one (strum::IntoStaticStr).
Adds just a counter counting up from the creation to the tenant, logged after activation. Might help guide us with the investigation of #4025.