Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review Metric Public API #2620

Closed
cijothomas opened this issue Nov 16, 2021 · 4 comments
Closed

Review Metric Public API #2620

cijothomas opened this issue Nov 16, 2021 · 4 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@cijothomas
Copy link
Member

Review the public API for metrics before the 1st stable release. Mark anything not required by spec as internal only.

@cijothomas cijothomas added the enhancement New feature or request label Nov 16, 2021
@cijothomas cijothomas added this to the 1.2.0 milestone Nov 16, 2021
@cijothomas
Copy link
Member Author

Calling out some API names which require discussion:

  1. SetMaxMetricPointsPerMetricStream

@cijothomas
Copy link
Member Author

cijothomas commented Apr 12, 2022

static OpenTelemetry.Metrics.MeterProviderExtensions.TryFindExporter(this OpenTelemetry.Metrics.MeterProvider provider, out T exporter) -> bool

Need to check this.. Looks like this is required for the Prometheus middleware.

@cijothomas
Copy link
Member Author

Closing this item, as the review is completed, and no unwanted public API remains now. (once 3161 is merged.)

@CodeBlanch
Copy link
Member

@alanwest @cijothomas We can do this later, but should we make this prop public get/set?

public PeriodicExportingMetricReaderOptions PeriodicExportingMetricReaderOptions { get; private set; } = new PeriodicExportingMetricReaderOptions();

Right now there is a private setter which is unusual I think for options classes in and out of our repo. I don't think IOptions will bind to a private setter, but not sure. Probably good to do just for consistency?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants