feat: enable Sentry Performance Profiling #257
+59
−1
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
Sentry docs: - https://docs.sentry.io/platforms/javascript/guides/node/tracing/ - https://docs.sentry.io/platforms/javascript/guides/node/tracing/instrumentation/automatic-instrumentation/ Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
juliangruber
approved these changes
Nov 22, 2024
|
Let's watch CPU usage after deploying |
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.
Setup Sentry Performance Profiling for spark-stats to allow us to learn why
are we hitting Fly's CPU throttling limits. Depending on the outcome of this
experiment, we can roll out profiling to other services, e.g. spark-observer.
Sentry docs: