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

Bump OpenTelemetry from 1.2.0-rc2 to 1.2.0 #1598

Merged
merged 1 commit into from
May 31, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 24, 2022

Bumps OpenTelemetry from 1.2.0-rc2 to 1.2.0.

Release notes

Sourced from OpenTelemetry's releases.

1.2.0 of Core Components

1st Stable Release of Metrics SDK. Same as 1.2.0-rc5, except the following changes.

OpenTelemetry

  • Make setter for MetricReaderOptions.PeriodicExportingMetricReaderOptions property public. (#3184)

OpenTelemetry.Exporter.OpenTelemetryProtocol

  • LogExporter to correctly map Severity to OTLP. (#3177)

  • LogExporter to special case {OriginalFormat} to populate Body. (#3182)

1.2.0-rc5 of Core Components

This is the final RC for 1.2.0 release. OpenTelemetry

  • Removed the Temporality setting on MetricReader and replaced it with TemporalityPreference. This is a breaking change. TemporalityPreference is used to determine the AggregationTemporality used on a per-instrument kind basis. Currently, there are two preferences:

    • Cumulative: Measurements from all instrument kinds are aggregated using AggregationTemporality.Cumulative.
    • Delta: Measurements from Counter, ObservableCounter, and Histogram instruments are aggregated using AggregationTemporality.Delta. When UpDownCounters are supported with DiagnosticSource version 7.0 onwards, they will be aggregated using AggregationTemporality.Cumulative. (#3153)
  • Fix issue where ExplicitBucketHistogramConfiguration could be used to configure metric streams for instruments that are not histograms. Currently, it is not possible to change the aggregation of an instrument with views. This may be possible in the future. (#3126)

  • Conformed to the specification to ensure that each view that an instrument matches results in a new metric stream. With this change it is possible for views to introduce conflicting metric streams. Any conflicts encountered will result in a diagnostic log. (#3148)

OpenTelemetry.Api

OpenTelemetry.Exporter.Console

... (truncated)

Commits
  • cab5b26 Prepare 1.2.0 stable release. (#3188)
  • 73cc937 Public setter for MetricReaderOptions.PeriodicExportingMetricReaderOptions (#...
  • c926c02 OTLP LogExporter to special case {OriginalFormat} to populate body (#3182)
  • ed3945d Prometheus exporter returns 204 No Content and logs warning on no metrics. (#...
  • 903cf1e OTLP Tests - Minor improvements (#3180)
  • 02301b6 Minor tweak to OTLP LogExporter tests (#3178)
  • a9d15c0 Fix severity mapping for OTLP Log Exporter (#3177)
  • 4ff7278 Bump actions/setup-dotnet from 1 to 2 (#3176)
  • 3deeda8 Bump actions/upload-artifact from 2 to 3 (#3175)
  • 81c427a Bump codecov/codecov-action from 1.0.12 to 3.0.0 (#3174)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [OpenTelemetry](https://github.com/open-telemetry/opentelemetry-dotnet) from 1.2.0-rc2 to 1.2.0.
- [Release notes](https://github.com/open-telemetry/opentelemetry-dotnet/releases)
- [Commits](open-telemetry/opentelemetry-dotnet@core-1.2.0-rc2...core-1.2.0)

---
updated-dependencies:
- dependency-name: OpenTelemetry
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 24, 2022
@rogeralsing rogeralsing merged commit 0e16fcf into dev May 31, 2022
@rogeralsing rogeralsing deleted the dependabot/nuget/OpenTelemetry-1.2.0 branch May 31, 2022 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant