Bump go.opentelemetry.io/otel/sdk from 0.20.0 to 1.3.0

[dependabot]

Bumps go.opentelemetry.io/otel/sdk from 0.20.0 to 1.3.0.

Release notes

Sourced from go.opentelemetry.io/otel/sdk's releases.

Release v1.1.0

Added

• Add the "go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc".WithGRPCConn option so the exporter can reuse an existing gRPC connection. (#2002)
• Add the go.opentelemetry.io/otel/semconv/v1.7.0 package. The package contains semantic conventions from the v1.7.0 version of the OpenTelemetry specification. (#2320)
• Add the go.opentelemetry.io/otel/semconv/v1.6.1 package. The package contains semantic conventions from the v1.6.1 version of the OpenTelemetry specification. (#2321)
• Add the go.opentelemetry.io/otel/semconv/v1.5.0 package. The package contains semantic conventions from the v1.5.0 version of the OpenTelemetry specification. (#2322)
  • When upgrading from the semconv/v1.4.0 package note the following name changes:
    • K8SReplicasetUIDKey -> K8SReplicaSetUIDKey
    • K8SReplicasetNameKey -> K8SReplicaSetNameKey
    • K8SStatefulsetUIDKey -> K8SStatefulSetUIDKey
    • k8SStatefulsetNameKey -> K8SStatefulSetNameKey
    • K8SDaemonsetUIDKey -> K8SDaemonSetUIDKey
    • K8SDaemonsetNameKey -> K8SDaemonSetNameKey

Changed

• Links added to a span will be dropped by the SDK if they contain an invalid span context (#2275).

Fixed

• The "go.opentelemetry.io/otel/semconv/v1.4.0".HTTPServerAttributesFromHTTPRequest now correctly only sets the HTTP client IP attribute even if the connection was routed with proxies and there are multiple addresses in the X-Forwarded-For header. (#2282, #2284)
• The "go.opentelemetry.io/otel/semconv/v1.4.0".NetAttributesFromHTTPRequest function correctly handles IPv6 addresses as IP addresses and sets the correct net peer IP instead of the net peer hostname attribute. (#2283, #2285)
• The simple span processor shutdown method deterministically returns the exporter error status if it simultaneously finishes when the deadline is reached. (#2290, #2289)

Release v1.0.0

This is the first stable release for the project. This release includes an API and SDK for the tracing signal that will comply with the stability guarantees defined by the projects versioning policy.

Added

• OTLP trace exporter now sets the SchemaURL field in the exported telemetry if the Tracer has WithSchemaURL option. (#2242)

Fixed

• Slice-valued attributes can correctly be used as map keys. (#2223)

Removed

• Removed the "go.opentelemetry.io/otel/exporters/zipkin".WithSDKOptions function. (#2248)
• Removed the deprecated package go.opentelemetry.io/otel/oteltest. (#2234)
• Removed the deprecated package go.opentelemetry.io/otel/bridge/opencensus/utils. (#2233)
• Removed deprecated functions, types, and methods from go.opentelemetry.io/otel/attribute package. Use the typed functions and methods added to the package instead. (#2235)
  • The Key.Array method is removed.
  • The Array function is removed.
  • The Any function is removed.

... (truncated)

Changelog

Sourced from go.opentelemetry.io/otel/sdk's changelog.

[1.3.0] - 2021-12-10

⚠️ Notice ⚠️

We have updated the project minimum supported Go version to 1.16

Added

• Added an internal Logger. This can be used by the SDK and API to provide users with feedback of the internal state. To enable verbose logs configure the logger which will print V(1) logs. For debugging information configure to print V(5) logs. (#2343)
• Add the WithRetry Option and the RetryConfig type to the go.opentelemetry.io/otel/exporter/otel/otlpmetric/otlpmetrichttp package to specify retry behavior consistently. (#2425)
• Add SpanStatusFromHTTPStatusCodeAndSpanKind to all semconv packages to return a span status code similar to SpanStatusFromHTTPStatusCode, but exclude 4XX HTTP errors as span errors if the span is of server kind. (#2296)

Changed

• The "go.opentelemetry.io/otel/exporter/otel/otlptrace/otlptracegrpc".Client now uses the underlying gRPC ClientConn to handle name resolution, TCP connection establishment (with retries and backoff) and TLS handshakes, and handling errors on established connections by re-resolving the name and reconnecting. (#2329)
• The "go.opentelemetry.io/otel/exporter/otel/otlpmetric/otlpmetricgrpc".Client now uses the underlying gRPC ClientConn to handle name resolution, TCP connection establishment (with retries and backoff) and TLS handshakes, and handling errors on established connections by re-resolving the name and reconnecting. (#2425)
• The "go.opentelemetry.io/otel/exporter/otel/otlpmetric/otlpmetricgrpc".RetrySettings type is renamed to RetryConfig. (#2425)
• The go.opentelemetry.io/otel/exporter/otel/* gRPC exporters now default to using the host's root CA set if none are provided by the user and WithInsecure is not specified. (#2432)
• Change resource.Default to be evaluated the first time it is called, rather than on import. This allows the caller the option to update OTEL_RESOURCE_ATTRIBUTES first, such as with os.Setenv. (#2371)

Fixed

• The go.opentelemetry.io/otel/exporter/otel/* exporters are updated to handle per-signal and universal endpoints according to the OpenTelemetry specification. Any per-signal endpoint set via an OTEL_EXPORTER_OTLP_<signal>_ENDPOINT environment variable is now used without modification of the path. When OTEL_EXPORTER_OTLP_ENDPOINT is set, if it contains a path, that path is used as a base path which per-signal paths are appended to. (#2433)
• Basic metric controller updated to use sync.Map to avoid blocking calls (#2381)
• The go.opentelemetry.io/otel/exporter/jaeger correctly sets the otel.status_code value to be a string of ERROR or OK instead of an integer code. (#2439, #2440)

Deprecated

• Deprecated the "go.opentelemetry.io/otel/exporter/otel/otlpmetric/otlpmetrichttp".WithMaxAttempts Option, use the new WithRetry Option instead. (#2425)
• Deprecated the "go.opentelemetry.io/otel/exporter/otel/otlpmetric/otlpmetrichttp".WithBackoff Option, use the new WithRetry Option instead. (#2425)

Removed

• Remove the metric Processor's ability to convert cumulative to delta aggregation temporality. (#2350)
• Remove the metric Bound Instruments interface and implementations. (#2399)
• Remove the metric MinMaxSumCount kind aggregation and the corresponding OTLP export path. (#2423)
• Metric SDK removes the "exact" aggregator for histogram instruments, as it performed a non-standard aggregation for OTLP export (creating repeated Gauge points) and worked its way into a number of confusing examples. (#2348)

[1.2.0] - 2021-11-12

Changed

• Metric SDK export.ExportKind, export.ExportKindSelector types have been renamed to aggregation.Temporality and aggregation.TemporalitySelector respectively to keep in line with current specification and protocol along with built-in selectors (e.g., aggregation.CumulativeTemporalitySelector, ...). (#2274)
• The Metric Exporter interface now requires a TemporalitySelector method instead of an ExportKindSelector. (#2274)
• Metrics API cleanup. The metric/sdkapi package has been created to relocate the API-to-SDK interface:
  • The following interface types simply moved from metric to metric/sdkapi: Descriptor, MeterImpl, InstrumentImpl, SyncImpl, BoundSyncImpl, AsyncImpl, AsyncRunner, AsyncSingleRunner, and AsyncBatchRunner

... (truncated)

Commits

• aedef05 Release prep v1.3.0 (#2441)
• b46019a Fix Jaeger exporter status conversion (#2440)
• 9312664 Fix per-signal endpoint parsing in OTLP exporters (#2433)
• b177541 Use host root CA set by default for OTLP exporter (#2432)
• 2b7c650 Merge pull request #2424 from MadVikingGod/refactor-errorhandler
• c351302 Merge branch 'main' into refactor-errorhandler
• a4f183b Remove metric MinMaxSumCount kind aggregation (#2423)
• ee60bcc Bump github.com/itchyny/gojq from 0.12.5 to 0.12.6 in /internal/tools (#2430)
• a7b3c37 Bump golang.org/x/tools from 0.1.7 to 0.1.8 in /internal/tools (#2429)
• ae76e71 Bump github.com/go-logr/logr from 1.2.0 to 1.2.1 (#2428)
• Additional commits viewable in compare view

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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}