Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feat: add a span processor to improve Next.js cardinality issues #957

Merged
merged 1 commit into from
Sep 27, 2024
Merged

feat: add a span processor to improve Next.js cardinality issues #957

merged 1 commit into from
Sep 27, 2024

Conversation

seemk
Copy link
Contributor

@seemk seemk commented Sep 27, 2024

  • Next.js produces spans with high cardinality names, containing the query parameters and dynamic route parts. This is an attempt to get rid of query parameters and set a proper route for the spans if one is available.
  • Can be enabled with SPLUNK_NEXTJS_FIX_ENABLED - disabled by default.

@seemk seemk requested review from a team as code owners September 27, 2024 10:27
@seemk seemk merged commit ed51731 into main Sep 27, 2024
129 checks passed
@seemk seemk deleted the nextjs-cardinality-fix branch September 27, 2024 10:44
@github-actions github-actions bot locked and limited conversation to collaborators Sep 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@mhennoch mhennoch mhennoch approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@seemk @mhennoch