-
Notifications
You must be signed in to change notification settings - Fork 463
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 2025 goals #10196
Error Tracking Q1 2025 goals #10196
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
* Fix query performance to make UI snappier | ||
* Implement issue threshold based alerting | ||
* Add build time symbol set upload support |
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.
These three and the "team based issue assignment" feel like four big features. Should we consider dropping one of them, if so which one?
Or maybe we drop the "Integrate with other products" goal. This feels like a secondary focus until we have a product that can stand on its own
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.
Agree dropping the "Integrate with other products" goal.
* Cymbal metric dashboards & alerts | ||
* Exclude $exception events from analytics billing | ||
* Fix query performance to make UI snappier | ||
* Implement issue threshold based alerting | ||
* Add build time symbol set upload support |
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.
Are all these really needed before we go to public beta? (I'm not saying they aren't - just pushing a bit to see if there's a way to get this in Beta faster)
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 we can (and should) go to an early access beta today given the number of people requesting access to the private beta. From customer interviews and the feedback we've had so far this is more the list of internal items & features for a more general v1 release
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.
LGTM
No description provided.