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.

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

Report ThreadPool stats #1399

Merged
merged 5 commits into from
Dec 22, 2021
Merged

Report ThreadPool stats #1399

merged 5 commits into from
Dec 22, 2021

Conversation

SimonCropp
Copy link
Contributor

fixes #938

@getsentry getsentry deleted a comment from github-actions bot Dec 16, 2021
@@ -56,6 +57,7 @@ public SentryEvent Process(SentryEvent @event)
}

AddMemoryInfo(@event.Contexts);
AddThreadPoolInfo(@event.Contexts);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bruno-garcia we only want that information for Events?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

forgive my ignorance, where else would we have it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe Lucas is referring to Transactions as the other possible place to add it.
We only run SentryEvent instances here so transactions won't be getting this information.

A few things go through when deciding:

  • Does this information help understand performance problems with the app?
  • Is it cheap to retrieve this information (as in resource intensiveness)?

If the answer is 'yes' to both, it's a good candidate. Ideally we add information that's relative to the transaction itself (like what happened during the duration of that transaction). Like: How many GC gen0/1/2 ran during the transaction, for example. As 'point in time' information alone within a transaction might not be as valuable.

Ultimately, this might be more useful only as Metrics. Which is something we'll look into adding in the future

@codecov-commenter
Copy link

codecov-commenter commented Dec 19, 2021

Codecov Report

Merging #1399 (fce497c) into main (3bb16d8) will decrease coverage by 1.28%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1399      +/-   ##
==========================================
- Coverage   84.04%   82.76%   -1.29%     
==========================================
  Files         217      218       +1     
  Lines        7310     7351      +41     
  Branches     1415     1415              
==========================================
- Hits         6144     6084      -60     
- Misses        727      835     +108     
+ Partials      439      432       -7     
Impacted Files Coverage Δ
src/Sentry/Internal/MainSentryEventProcessor.cs 93.51% <100.00%> (+0.81%) ⬆️
src/Sentry/Internal/ThreadPoolInfo.cs 100.00% <100.00%> (ø)
src/Sentry/PlatformAbstractions/FrameworkInfo.cs 0.00% <0.00%> (-100.00%) ⬇️
...ntry/PlatformAbstractions/RegistryKeyExtensions.cs 0.00% <0.00%> (-100.00%) ⬇️
...Sentry/PlatformAbstractions/FrameworkInfo.NetFx.cs 0.00% <0.00%> (-70.43%) ⬇️
...rmAbstractions/NetFxInstallationsEventProcessor.cs 4.54% <0.00%> (-68.19%) ⬇️
...ntry/PlatformAbstractions/FrameworkInstallation.cs 25.00% <0.00%> (-37.50%) ⬇️
...ntry/Integrations/NetFxInstallationsIntegration.cs 28.57% <0.00%> (-28.58%) ⬇️
src/Sentry/PlatformAbstractions/RuntimeInfo.cs 53.44% <0.00%> (-5.18%) ⬇️
src/Sentry/Exceptions/Mechanism.cs 82.35% <0.00%> (-2.95%) ⬇️
... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3bb16d8...fce497c. Read the comment docs.

@SimonCropp SimonCropp merged commit 356eaf6 into main Dec 22, 2021
@SimonCropp SimonCropp deleted the Report-ThreadPool-stats branch December 22, 2021 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Report ThreadPool stats
4 participants