-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
feat(aci): Add metric issue event details #103995
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(aci): Add metric issue event details #103995
Conversation
static/app/views/issueDetails/streamline/sidebar/metricDetectorTriggeredSection.tsx
Show resolved
Hide resolved
| </ErrorBoundary> | ||
| </Fragment> | ||
| )} | ||
| {issueTypeConfig.metricDetectorTriggered.enabled && ( |
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 don't need this, since we check that the event has a specific property
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.
we've been trying to use the event to decide what to render where possible
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.
Okay yeah good call, using the data source type now to make the determination
static/app/views/issueDetails/streamline/sidebar/metricDetectorTriggeredSection.tsx
Show resolved
Hide resolved
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Adds something to the metric issue event details so it doesn't look so broken and tells the user why it triggered. Much more to add in the future, but this is a start