[frontend] open-telemetry setup #419
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sebastien-comeau
force-pushed
the
open-telemetry-setup
branch
from
90933e5
to
4c46988
Compare
sebastien-comeau
force-pushed
the
open-telemetry-setup
branch
3 times, most recently
from
15d61cc
to
5d1db5a
Compare
sebastien-comeau
force-pushed
the
open-telemetry-setup
branch
from
5d1db5a
to
91941c9
Compare
gregory-j-baker
approved these changes
Jun 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
List of proposed changes:
Additional Notes
Doing it that way fixes @sebastien-comeau issues when stopping next dev process. He has terminal piling over and over and could only stop them manually with task manager. Implemented Next.js OpenTelemetry guide fixed the issue.
https://nextjs.org/docs/app/building-your-application/optimizing/open-telemetry