chore: Add Metrics support for Web projects using native dependency injection #21
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.
Description of changes:
One of our early discussions was if we should target a simple Lambda function or a typical .NET web project. Now that I have more experience working with AWS customers using .NET I see them using both patterns so I decided to implement both.
For a simple Lambda Function you have to initialize a static MetricsLogger and flush the data by the end of the execution.
As an alternative it can also be flushed automatically when the Metrics Logger object is disposed.
For web projects, I have created a ServiceCollectionExtension and ApplicationBuilderExtension to support native dependency injection. For this to work the developer just needs to add it to the startup file.
With this configuration, developers can now use the MetricsLogger on their code like so.
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.