Uh oh!
There was an error while loading. Please reload this page.
Add experimental profiler under experiments.enable_profiling - #1481
Conversation
Uh oh!
There was an error while loading. Please reload this page.
sl0thentr0py
commented
Jun 29, 2022
@szokeasaurusrex could you add output from a sample run here for completeness? |
szokeasaurusrex
commented
Jun 29, 2022
Here is a sample output from profiling a Flask request. Please be aware that I am currently working on changing the output format to a JSON format that will enable us to view the profile flamegraphs in Sentry. |
Uh oh!
There was an error while loading. Please reload this page.
sl0thentr0py
left a comment
There was a problem hiding this comment.
again some minor code style, everything looks good otherwise!
very cool work :)
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
sl0thentr0py
left a comment
There was a problem hiding this comment.
let's move this to experimental.
also, can you add at least one integration test here that when the experimental flag is on, you get the profiling object in the envelope.
(ping me if you can't figure out how to do something in pytest)
| auto_enabling_integrations=True, # type: bool | ||
| auto_session_tracking=True, # type: bool | ||
| send_client_reports=True, # type: bool | ||
| enable_profiling=False, # type: bool |
There was a problem hiding this comment.
we decided this should move to experimental so please move it here
sentry-python/sentry_sdk/consts.py
Lines 29 to 39 in 9e69fcf
and change the checks in the context manager and tracing.py accordingly
szokeasaurusrex
commented
Jul 22, 2022
@sl0thentr0py I moved the |
To validate the profiler, I used this Flask server (which is just a script used by the profiling team that has been wrapped within a Flask server). To verify profiles were being generated and uploaded, I ran the Flask server in single-threaded mode with I also validated that a multi-threaded server would not break with the profiler enabled. To perform this verification, I ran the server in multi-threaded mode with |

No description provided.