Bump github.com/open-telemetry/opentelemetry-collector-contrib/confmap/provider/s3provider from 0.100.0 to 0.101.0 in /collector in the opentelemetry-deps-collector group across 1 directory

[dependabot]

Bumps the opentelemetry-deps-collector group with 1 update in the /collector directory: github.com/open-telemetry/opentelemetry-collector-contrib/confmap/provider/s3provider.

Updates github.com/open-telemetry/opentelemetry-collector-contrib/confmap/provider/s3provider from 0.100.0 to 0.101.0

Release notes

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/confmap/provider/s3provider's releases.

v0.101.0

The OpenTelemetry Collector Contrib contains everything in the opentelemetry-collector release, be sure to check the release notes there as well.

End User Changelog

🛑 Breaking changes 🛑

• sumologicexporter: change logs behavior (#31479)

  • set OTLP as default format
  • add support for OTLP format
  • do not support metadata attributes
  • do not support source headers

• sumologicexporter: change metrics behavior (#31479)

  • remove suppport for carbon2 and graphite
  • add support for otlp format
  • do not support metadata attributes
  • do not support source headers
  • set otlp as default metrics format

• sumologicexporter: remove deprecated configuration options (#32315) migration has been described in the following document https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.100.0/exporter/sumologicexporter#migration-to-new-architecture

• remotetapprocessor: Make the limit configuration work properly. (#32385) The limit configuration was ignored previously, but now it works according to the configuration and documentation. Nothing is required of users. See the remotetapprocessor's README.md for details.

• groupbytraceprocessor: Fix groupbytrace metrics contain duplicate prefix (#32698)

• vcenterreceiver: Removes vcenter.cluster.name attribute from vcenter.datastore metrics (#32674) If there were multiple Clusters, Datastore metrics were being repeated under Resources differentiated with a vcenter.cluster.name resource attribute. In the same vein, if there were standalone Hosts, in addition to clusters the metrics would be repeated under a Resource without the vcenter.cluster.name attribute. Now there will only be a single set of metrics for one Datastore (as there should be, as Datastores don't belong to Clusters).

• resourcedetectionprocessor: Move processor.resourcedetection.hostCPUModelAndFamilyAsString feature gate to stable. (#29025)

• filelog, journald, tcp, udp, syslog, windowseventlog receivers: The internal logger has been changed from zap.SugaredLogger to zap.Logger. (#32177) This should not have any meaningful impact on most users but the logging format for some logs may have changed.

• awsxrayexporter: change x-ray exporter's translator to make "." split annotation pass as-is (#32694, #31732) This change make below change to beta stage for feature gate 'exporter.xray.allowDot'，this change will let the change mention below enable by default | In the past, X-Ray doesn’t support “.”. So we have a translator in x-ray export to translates it to “_” before sending traces to X-Ray Service. | To match otel naming style, x-ray service team decide to change their service to support both "." type and "" type of naming. In this case the translator that translate "." to "" is no-longer needed. This PR change the way this translator work | X-Ray PMs agree on rolling out this change by using feature-gate

🚀 New components 🚀

• awss3receiver: Initial implementation of the AWS S3 receiver. (#30750)

• receiver/mysql: Adds INFORMATION_SCHEMA TABLES metrics (#32693) This adds table size metrics using the INFORMATION_SCHEMA TABLES table: https://dev.mysql.com/doc/refman/8.3/en/information-schema-tables-table.html. Specifically, we are adding the columns: TABLE_ROWS, AVG_ROW_LENGTH, DATA_LENGTH, INDEX_LENGTH.

• exporter/otelarrow: Implementation copied from opentelemetry/otel-arrow repository @​v0.23.0. (#26491)

... (truncated)

Changelog

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/confmap/provider/s3provider's changelog.

v0.101.0

🛑 Breaking changes 🛑

• opampextension: Move custom message interfaces to separate package (#32950) Moves CustomCapabilityRegistry, CustomCapabilityHandler, and CustomCapabilityRegisterOption to a new module. These types can now be found in the new github.com/open-telemetry/opentelemetry-collector-contrib/extension/opampcustommessages module.

• pkg/stanza: The internal logger has been changed from zap.SugaredLogger to zap.Logger. (#32177) Functions accepting a SugaredLogger, and fields of type SugaredLogger, have been deprecated.

💡 Enhancements 💡

• testbed: Add the use of connectors to the testbed (#30165)

Commits

• c0b5113 [chore] Prepare release 0.101.0 (#33164)
• ab4090f [CI] fix timeout on arm-unittest-matrix (#32948)
• 63b21d2 [core] Prepare v0.101.0 (#33142)
• 0491cd0 Update codecov/codecov-action action to v4.4.1 (#33143)
• feae9ac [chore][pkg/ottl] Minor update to Concat readme (#33131)
• 7ddb350 [receiver/mysql] feat: add table size metrics (#32680)
• cd916df [chore] Bump github.com/DataDog/viper to v1.13.3 (#33133)
• 726ffec [chore] Remove djaglowski as codeowner of aws and azure receivers (#33128)
• f876d49 [receiver/sqlserver] Add database status metric (#33064)
• 6eaf435 [chore]: healthcheckv2extension remove toolchain requirement (#33127)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions