Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc from 1.4.1 to 1.5.0 in /example

[dependabot]

Bumps go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc from 1.4.1 to 1.5.0.

Release notes

Sourced from go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc's releases.

Release v1.5.0

Added

• Log the Exporters configuration in the TracerProviders message. (#2578)

• Added support to configure the span limits with environment variables. The following environment variables are supported. (#2606, #2637)

  • OTEL_SPAN_ATTRIBUTE_VALUE_LENGTH_LIMIT
  • OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT
  • OTEL_SPAN_EVENT_COUNT_LIMIT
  • OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT
  • OTEL_SPAN_LINK_COUNT_LIMIT
  • OTEL_LINK_ATTRIBUTE_COUNT_LIMIT

  If the provided environment variables are invalid (negative), the default values would be used.

• Rename the gc runtime name to go (#2560)

• Add resource container ID detection. (#2418)

• Add span attribute value length limit. The new AttributeValueLengthLimit field is added to the "go.opentelemetry.io/otel/sdk/trace".SpanLimits type to configure this limit for a TracerProvider. The default limit for this resource is "unlimited". (#2637)

• Add the WithRawSpanLimits option to go.opentelemetry.io/otel/sdk/trace. This option replaces the WithSpanLimits option. Zero or negative values will not be changed to the default value like WithSpanLimits does. Setting a limit to zero will effectively disable the related resource it limits and setting to a negative value will mean that resource is unlimited. Consequentially, limits should be constructed using NewSpanLimits and updated accordingly. (#2637)

Changed

• Drop oldest tracestate Member when capacity is reached. (#2592)
• Add event and link drop counts to the exported data from the oltptrace exporter. (#2601)
• Unify path cleaning functionally in the otlpmetric and otlptrace configuration. (#2639)
• Change the debug message from the sdk/trace.BatchSpanProcessor to reflect the count is cumulative. (#2640)
• Introduce new internal envconfig package for OTLP exporters. (#2608)
• If http.Request.Host is empty, fall back to use URL.Host when populating http.host in the semconv packages. (#2661)

Fixed

• Remove the OTLP trace exporter limit of SpanEvents when exporting. (#2616)
• Default to port 4318 instead of 4317 for the otlpmetrichttp and otlptracehttp client. (#2614, #2625)
• Unlimited span limits are now supported (negative values). (#2636, #2637)

Deprecated

• Deprecated "go.opentelemetry.io/otel/sdk/trace".WithSpanLimits. Use WithRawSpanLimits instead. That option allows setting unlimited and zero limits, this option does not. This option will be kept until the next major version incremented release. (#2637)

Changelog

Sourced from go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc's changelog.

[1.5.0] - 2022-03-16

Added

• Log the Exporters configuration in the TracerProviders message. (#2578)

• Added support to configure the span limits with environment variables. The following environment variables are supported. (#2606, #2637)

  • OTEL_SPAN_ATTRIBUTE_VALUE_LENGTH_LIMIT
  • OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT
  • OTEL_SPAN_EVENT_COUNT_LIMIT
  • OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT
  • OTEL_SPAN_LINK_COUNT_LIMIT
  • OTEL_LINK_ATTRIBUTE_COUNT_LIMIT

  If the provided environment variables are invalid (negative), the default values would be used.

• Rename the gc runtime name to go (#2560)

• Add resource container ID detection. (#2418)

• Add span attribute value length limit. The new AttributeValueLengthLimit field is added to the "go.opentelemetry.io/otel/sdk/trace".SpanLimits type to configure this limit for a TracerProvider. The default limit for this resource is "unlimited". (#2637)

• Add the WithRawSpanLimits option to go.opentelemetry.io/otel/sdk/trace. This option replaces the WithSpanLimits option. Zero or negative values will not be changed to the default value like WithSpanLimits does. Setting a limit to zero will effectively disable the related resource it limits and setting to a negative value will mean that resource is unlimited. Consequentially, limits should be constructed using NewSpanLimits and updated accordingly. (#2637)

Changed

• Drop oldest tracestate Member when capacity is reached. (#2592)
• Add event and link drop counts to the exported data from the oltptrace exporter. (#2601)
• Unify path cleaning functionally in the otlpmetric and otlptrace configuration. (#2639)
• Change the debug message from the sdk/trace.BatchSpanProcessor to reflect the count is cumulative. (#2640)
• Introduce new internal envconfig package for OTLP exporters. (#2608)
• If http.Request.Host is empty, fall back to use URL.Host when populating http.host in the semconv packages. (#2661)

Fixed

• Remove the OTLP trace exporter limit of SpanEvents when exporting. (#2616)
• Default to port 4318 instead of 4317 for the otlpmetrichttp and otlptracehttp client. (#2614, #2625)
• Unlimited span limits are now supported (negative values). (#2636, #2637)

Deprecated

• Deprecated "go.opentelemetry.io/otel/sdk/trace".WithSpanLimits. Use WithRawSpanLimits instead. That option allows setting unlimited and zero limits, this option does not. This option will be kept until the next major version incremented release. (#2637)

Commits

• 2cfc521 Release v1.5.0 (#2676)
• b229997 Bump google.golang.org/grpc from 1.44.0 to 1.45.0 in /exporters/otlp/otlptrac...
• b1d2978 Bump google.golang.org/grpc from 1.44.0 to 1.45.0 in /exporters/otlp/otlpmetr...
• 27633f0 Bump google.golang.org/grpc from 1.44.0 to 1.45.0 in /example/otel-collector ...
• 005eefe [website_docs] Fix link intra-site link refs (#2666)
• d3ab885 Update otel-collector example readme (#2662)
• 68e2495 fallback to URL.Host if Request.Host is empty (#2661)
• 0e4c156 double benchmark alert threshold (#2649)
• 16e52ed Fix typo in go libraries (#2652)
• d6f9d0d Bump actions/checkout from 2.4.0 to 3 (#2645)
• 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)

[MrAlias]

@dependabot rebase