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

chore(deps): update opentelemetry-dotnet monorepo to 1.9.0 #3

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
OpenTelemetry.Exporter.Console (source) 1.7.0 -> 1.9.0 age adoption passing confidence
OpenTelemetry.Extensions.Hosting (source) 1.7.0 -> 1.9.0 age adoption passing confidence

Release Notes

open-telemetry/opentelemetry-dotnet (OpenTelemetry.Exporter.Console)

v1.9.0

  • Exemplars are now part of the stable API! For details see: customizing
    exemplars
    collection
    .

  • WithLogging is now part of the stable API! Logging, Metrics, and Tracing can
    now all be configured using the With style and the builders finally have
    parity in their APIs.

v1.8.0

  • TracerProvider sampler can now be configured via the OTEL_TRACES_SAMPLER &
    OTEL_TRACES_SAMPLER_ARG envvars.

  • A new UseOtlpExporter cross-cutting extension has been added to register the
    OtlpExporter and enable all signals in a single call.

  • exception.type, exception.message, exception.stacktrace will now
    automatically be included by the OtlpLogExporter when logging exceptions.
    Previously an experimental environment variable had to be set.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 3b08bbd to edf2a72 Compare April 3, 2024 00:31
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to v1.7.1 chore(deps): update opentelemetry-dotnet monorepo Apr 3, 2024
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from edf2a72 to 0d742ab Compare April 4, 2024 21:48
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo chore(deps): update opentelemetry-dotnet monorepo to v1.8.0 Apr 4, 2024
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 0d742ab to f71cbda Compare April 12, 2024 22:24
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to v1.8.0 chore(deps): update opentelemetry-dotnet monorepo Apr 12, 2024
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from f71cbda to 1e3cb70 Compare April 18, 2024 03:58
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo chore(deps): update opentelemetry-dotnet monorepo to v1.8.1 Apr 18, 2024
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 1e3cb70 to 506d31a Compare June 15, 2024 11:37
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to v1.8.1 chore(deps): update opentelemetry-dotnet monorepo Jun 15, 2024
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo chore(deps): update opentelemetry-dotnet monorepo to v1.9.0 Jun 19, 2024
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to v1.9.0 chore(deps): update opentelemetry-dotnet monorepo to 1.9.0 Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants