Skip to content

Conversation

timothycoleman
Copy link
Contributor

Cherry pick of #5198

This message just executes an Action and it is used by a few places in Projections. When it triggers a SLOW QUEUE MESSAGE log, it's not clear what it was actually doing. This extra logging points to the action being performed.

e.g.

[41392,47,08:04:39.252,DBG] QueuedHandlerThreadPool        SLOW QUEUE MSG [Projection Core #1]: UnwrapEnvelopeMessage - 1ms. Q: 8/32. EventStore.Projections.Core.Messaging.UnwrapEnvelopeMessage, Extra Information: ReadAllEventsForward.

This message just executes an Action and it is used by a few places in Projections.
When it triggers a SLOW QUEUE MESSAGE log, it's not clear what it was actually doing.
This extra logging points to the action being performed.

e.g.
```
[41392,47,08:04:39.252,DBG] QueuedHandlerThreadPool        SLOW QUEUE MSG [Projection Core #1]: UnwrapEnvelopeMessage - 1ms. Q: 8/32. EventStore.Projections.Core.Messaging.UnwrapEnvelopeMessage, Extra Information: ReadAllEventsForward.
```
@timothycoleman timothycoleman requested a review from a team as a code owner July 23, 2025 12:44
@timothycoleman timothycoleman changed the title Add extra logging when UnwrapEnvelopeMessage is slow (#5198) [master] Add extra logging when UnwrapEnvelopeMessage is slow (#5198) Jul 23, 2025
Copy link
Contributor

Qodana for .NET

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

@timothycoleman timothycoleman merged commit b890245 into master Jul 24, 2025
11 of 15 checks passed
@timothycoleman timothycoleman deleted the cherry-pick/5198/timothycoleman/unwrap-envelope-message-extra-logging-master branch July 24, 2025 07:29
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.

2 participants