-
Notifications
You must be signed in to change notification settings - Fork 717
Error tracking Q1 goals #14132
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
Error tracking Q1 goals #14132
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ablaszkiewicz
left a comment
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.
I think it won't take me whole Q1 to do what's described in spikes & digest. Happy to look at the loading speed / moving issues to CH / recommendations.
|
@ablaszkiewicz I added an engagement section for moving issues to CH. For the loading speed, I think the first step would be to monitor it with the relevant breakdowns first to know how we can improve it (In monitoring section). |
fivestarspicy
left a comment
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.
looks good to me!
Changes
Add Error tracking goals for Q1 2026. I tried to stick to categories we would like to monitor, so we can see if the actions actually moved the needle, but let me know if it does not make sense to you or if you want to adjust.