Skip to content
This repository has been archived by the owner on Aug 3, 2024. It is now read-only.
/ ServerCommon Public archive

Improve SubscriptionProcessor's telemetry for messages exceeding expected duration #230

Merged
merged 2 commits into from
Nov 26, 2018

Conversation

loic-sharma
Copy link
Contributor

@loic-sharma loic-sharma commented Nov 21, 2018

Today, we have to parse Application Insights logs to figure out how a message handler's duration. This makes it impossible to dashboard and monitor. This metric will let us detect messages that caused deadlettering by exceeding their expected duration.

I also fixed a bunch of build warnings as part of this change.

Part of: NuGet/NuGetGallery#6624
Build: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=2228537&view=logs

@loic-sharma loic-sharma changed the title Track the time SubscriptionProcessor's handlers take to handle a message Improve SubscriptionProcessor's telemetry for messages exceeding expected duration Nov 21, 2018
@loic-sharma loic-sharma merged commit 3f719f1 into master Nov 26, 2018
@loic-sharma loic-sharma deleted the loshar-locks branch November 26, 2018 21:38
loic-sharma added a commit to NuGet/NuGet.Jobs that referenced this pull request Nov 27, 2018
Today, we have to parse Application Insights logs to figure out how a message handler's duration. This makes it impossible to dashboard and monitor. This metric will let us detect messages that caused deadlettering by exceeding their expected duration.

Depends on NuGet/ServerCommon#230
Part of NuGet/NuGetGallery#6624
joelverhagen pushed a commit to NuGet/NuGet.Jobs that referenced this pull request Oct 26, 2020
Today, we have to parse Application Insights logs to figure out how a message handler's duration. This makes it impossible to dashboard and monitor. This metric will let us detect messages that caused deadlettering by exceeding their expected duration.

Depends on NuGet/ServerCommon#230
Part of NuGet/NuGetGallery#6624
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants