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.
Due to the popularity of Refitter, I reach my monthly cap on Exceptionless after just a few days into the month. Exceptionless was kind enough to sponsor me with 15k events a month, which was fine when Refitter was initially released but now, Refitter has 150k weekly usages which is way above the 15k monthly cap.
This pull request includes changes to the
src/Refitter/Analytics.cs
andsrc/Refitter/GenerateCommand.cs
files to improve the logging mechanism by removing asynchronous calls and simplifying the code. The most important changes are summarized below:Improvements to logging mechanism:
LogFeatureUsage
method fromTask
tovoid
and removed the asynchronous call toExceptionlessClient.Default.ProcessQueueAsync
insrc/Refitter/Analytics.cs
. [1] [2]ExceptionlessClient.Default.CreateFeatureUsage
and its related code inLogFeatureUsage
method, opting to usetelemetryClient.TrackEvent
instead insrc/Refitter/Analytics.cs
. [1] [2]Code simplification:
ExecuteAsync
method insrc/Refitter/GenerateCommand.cs
to call the now synchronousLogFeatureUsage
method.