-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix(insights): Handle null span.group in Backend Insights widgets #112379
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
Changes from 4 commits
8aabafc
e37778b
d011829
d57dc32
b122243
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -39,7 +39,7 @@ export default function OverviewSlowNextjsSSRWidget(props: LoadableChartWidgetPr | |
| const pageFilterChartParams = usePageFilterChartParams(); | ||
| const {query} = useTransactionNameQuery(); | ||
|
|
||
| const fullQuery = `span.op:function.nextjs ${query}`; | ||
| const fullQuery = `has:span.group span.op:function.nextjs ${query}`; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: Looking at Is one better/preferred than the other?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's better to use the enum values because that makes it easier to find all usages of a specific attribute, but I always forget to do that! I can update |
||
|
|
||
| const spansRequest = useSpans( | ||
| { | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.