[Metrics] Improve dependency injection support in meter provider build-up using SDK#3646
Merged
CodeBlanch merged 12 commits intoopen-telemetry:mainfrom Sep 12, 2022
Merged
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #3646 +/- ##
==========================================
+ Coverage 87.29% 87.49% +0.19%
==========================================
Files 282 284 +2
Lines 10132 10195 +63
==========================================
+ Hits 8845 8920 +75
+ Misses 1287 1275 -12
|
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
Brings
MeterProviderBuilderup to ~parity withTracerProviderBuilderchanges from #3533.SDK public API
namespace Microsoft.Extensions.DependencyInjection { + public static class MeterProviderBuilderServiceCollectionExtensions + { // These are basically what existed previously in Hosting minus the IHostedService registration + public static IServiceCollection ConfigureOpenTelemetryMetrics(this IServiceCollection services) {} + public static IServiceCollection ConfigureOpenTelemetryMetrics(this IServiceCollection services, Action<MeterProviderBuilder> configure) {} + } } namespace OpenTelemetry.Metrics { public static class MeterProviderBuilderExtensions { // These existed previously in Hosting, now they are part of the SDK and can be used anywhere SDK is referenced + public static MeterProviderBuilder AddInstrumentation<T>(this MeterProviderBuilder meterProviderBuilder) {} + public static MeterProviderBuilder AddReader<T>(this MeterProviderBuilder meterProviderBuilder) where T : MetricReader {} + public static MeterProviderBuilder ConfigureBuilder(this MeterProviderBuilder meterProviderBuilder, Action<IServiceProvider, MeterProviderBuilder> configure) {} + public static MeterProviderBuilder ConfigureServices(this MeterProviderBuilder meterProviderBuilder, Action<IServiceCollection> configure) {} } }OpenTelemetry.Extensions.Hosting public API
namespace OpenTelemetry.Trace { public static class MeterProviderBuilderExtensions { - public static MeterProviderBuilder AddInstrumentation<T>(this MeterProviderBuilder meterProviderBuilder) {} - public static MeterProviderBuilder AddReader<T>(this MeterProviderBuilder meterProviderBuilder) where T : MetricReader {} - public static MeterProvider Build(this MeterProviderBuilder meterProviderBuilder, IServiceProvider serviceProvider) {} // Obsoleted these so no one breaks upgrading + [Obsolete("Call ConfigureBuilder instead this method will be removed in a future version.")] public static MeterProviderBuilder Configure(this MeterProviderBuilder meterProviderBuilder, Action<IServiceProvider, MeterProviderBuilder> configure) {} + [Obsolete("Call ConfigureServices instead this method will be removed in a future version.")] public static IServiceCollection? GetServices(this MeterProviderBuilder meterProviderBuilder) {} } }Existing scenarios made available in SDK
New scenarios enabled
AddExporter?
For logs + traces we have
AddExporterextensions. I didn't add one for metrics. @alanwest and I tried to figure out how it would work, but it is more complicated for metrics. There isn't the same concept of simple/batch processor type and exporters can be push, pull, or both. We decided to tackle this separately or not at all.Detached configuration method
Some users like @martinjt have asked for a way to configure things completely detached from the builder.
The SDK
ConfigureOpenTelemetryMetricsextension is safe to be called multiple times. Only oneMeterProviderwill exist in theIServiceProviderand multiple calls will all contribute to its configuration, in order. This makes it possible to detach from theMeterProviderBuilder. This enables a scenario like this...TODOs
CHANGELOG.mdupdated for non-trivial changes