build(deps): bump go.opentelemetry.io/otel from 1.43.0 to 1.44.0

[dependabot]

Bumps go.opentelemetry.io/otel from 1.43.0 to 1.44.0.

Changelog

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

[1.44.0/0.66.0/0.20.0/0.0.17] 2026-05-27

Added

• Add ByteSlice and ByteSliceValue functions for new BYTESLICE attribute type in go.opentelemetry.io/otel/attribute. (#7948)
• Apply attribute value limit to the KindBytes attribute type in go.opentelemetry.io/otel/sdk/log. (#7990)
• Apply attribute value limit to the BYTESLICE attribute type in go.opentelemetry.io/otel/sdk/trace. (#7990)
• Support BYTESLICE attributes in go.opentelemetry.io/otel/trace. (#8153)
• Support BYTESLICE attributes in go.opentelemetry.io/otel/exporters/otlp/otlptrace. (#8153)
• Support BYTESLICE attributes in go.opentelemetry.io/otel/exporters/otlp/otlplog. (#8153)
• Support BYTESLICE attributes in go.opentelemetry.io/otel/exporters/otlp/otlpmetric. (#8153)
• Support BYTESLICE attributes in go.opentelemetry.io/otel/exporters/zipkin. (#8153)
• Add String method for Value type in go.opentelemetry.io/otel/attribute. (#8142)
• Add Slice and SliceValue functions for new SLICE attribute type in go.opentelemetry.io/otel/attribute. (#8166)
• Support SLICE attributes in go.opentelemetry.io/otel/exporters/otlp/otlptrace. (#8216)
• Support SLICE attributes in go.opentelemetry.io/otel/exporters/otlp/otlplog. (#8216)
• Support SLICE attributes in go.opentelemetry.io/otel/exporters/otlp/otlpmetric. (#8216)
• Support SLICE attributes in go.opentelemetry.io/otel/exporters/zipkin. (#8216)
• Apply AttributeValueLengthLimit to attribute.SLICE type attribute values in go.opentelemetry.io/otel/sdk/trace, recursively truncating contained string values. (#8217)
• Add Error field on Record type in go.opentelemetry.io/otel/log/logtest. (#8148)
• Add WithMaxRequestSize option in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc. (#8157)
• Add WithMaxRequestSize option in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp. (#8157)
• Add WithMaxRequestSize option in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc. (#8157)
• Add WithMaxRequestSize option in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp. (#8157)
• Add WithMaxRequestSize option in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc. (#8157)
• Add WithMaxRequestSize option in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp. (#8157)
• Add Settable to go.opentelemetry.io/otel/metric/x to allow reusing attribute options. (#8178)
• Add experimental support for splitting metric data across multiple batches in go.opentelemetry.io/otel/sdk/metric. Set OTEL_GO_X_METRIC_EXPORT_BATCH_SIZE=<max_size> to enable for all periodic readers. See go.opentelemetry.io/otel/sdk/metric/internal/x for feature documentation. (#8071)
• Add experimental self-observability metrics in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc. Enable with OTEL_GO_X_SELF_OBSERVABILITY=true environment variable. See go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc/internal/x for feature documentation. (#8192)
• Add experimental self-observability metrics in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp. Enable with OTEL_GO_X_SELF_OBSERVABILITY=true environment variable. See go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp/internal/x for feature documentation. (#8194)
• Add experimental self-observability metrics in go.opentelemetry.io/otel/exporters/stdout/stdoutlog. Enable with OTEL_GO_X_SELF_OBSERVABILITY=true environment variable. See go.opentelemetry.io/otel/stdout/stdoutlog/internal/x for feature documentation. (#8263)
• Add WithDefaultAttributes to go.opentelemetry.io/otel/metric/x to support setting default attributes on instruments. (#8135)
• Add go.opentelemetry.io/otel/semconv/v1.41.0 package. The package contains semantic conventions from the v1.41.0 version of the OpenTelemetry Semantic Conventions. See the migration documentation for information on how to upgrade from go.opentelemetry.io/otel/semconv/v1.40.0. (#8324)
• Add Observable variants of instruments to go.opentelemetry.io/otel/semconv/v1.41.0 package. (#8350)
• Generate explicit histogram bucket boundaries from weaver configuration for HTTP and RPC duration instruments in go.opentelemetry.io/otel/semconv/v1.41.0. (#8002)

Changed

• ⚠️ Breaking Change: go.opentelemetry.io/otel/sdk/metric now applies a default cardinality limit of 2000 to comply with the Metrics SDK specification recommendation. New attribute sets are dropped when the cardinality limit is reached. The measurement of these sets are aggregated into a special attribute set containing attribute.Bool("otel.metric.overflow", true).

... (truncated)

Commits

• b62d928 Release 1.44.0 (#8376)
• 94132a0 chore(deps): update golang.org/x/telemetry digest to 5997936 (#8379)
• 6fdcf82 feat: add self-observability metrics to otlpmetricgrpc metric exporters (#8192)
• 761bbfc fix(deps): update golang.org/x (#8377)
• 3a91dc6 fix(deps): update googleapis to 3dc84a4 (#8375)
• f593185 exporters/otlp: default max request size to 64 MiB (#8365)
• f02feac Merge commit from fork
• 36c2f1b semconvkit: add invariant test for histogram-exclusion rule (#8370)
• d0b6cbd sdk/metric: document unit-sensitivity of DefaultAggregationSelector (#8224)
• 9a68034 add self observability for stdout exporter (#8263)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[github-actions]

TL;DR

check-ci failed on commit 6a37f48 because the dependency bump left module metadata incomplete (go mod tidy required). The immediate fix is to include the post-dependabot module sync updates and rerun CI.

Remediation

• Keep the follow-up dependabot commit ed0b9c9 (it adds the missing module sync updates in testing/go.mod, testing/go.sum, NOTICE.txt, and NOTICE-fips.txt) and rerun Buildkite for this PR.
• If you need to reproduce locally: run go mod tidy at repo root and under testing/, then regenerate notices with mage check:notice.

Investigation details

Root Cause

Classification: Dependency issue.

The failed build ran against commit 6a37f48a74f7090defe630e5d4c8bdd4b0a474bc, which only modified go.mod and go.sum for the otel bump. Fleet Server has a second Go module under testing/, and it still referenced the previous otel versions (testing/go.mod lines 93-94 on base state), so check-ci hit readonly module drift and aborted with go: updates to go.mod needed; to update it: go mod tidy.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/14912
• Job/step: Run check-ci (.buildkite/scripts/check_ci.sh)
• Commit under test: 6a37f48a74f7090defe630e5d4c8bdd4b0a474bc
• Key log excerpt:
  • go: updates to go.mod needed; to update it:
  • go mod tidy
• Commit file list for 6a37f48: only go.mod, go.sum
• PR head now includes follow-up commit ed0b9c9 (“Post dependabot file modifications”) which adds the missing module/notice updates.

Verification

• Not run in this workflow (analysis is based on Buildkite logs and PR commit/diff metadata).

Follow-up

• After rerun, if CI still fails, attach the new failing step log and I can map it to the next concrete fix.

Note

🔒 Integrity filter blocked 3 items

The following items were blocked because they don't meet the GitHub integrity level.

• build(deps): bump go.opentelemetry.io/otel from 1.43.0 to 1.44.0 #7119 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• build(deps): bump go.opentelemetry.io/otel from 1.43.0 to 1.44.0 #7119 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• 02e285f list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

@Mergifyio backport 9.4 9.3 8.19

[mergify]

backport 9.4 9.3 8.19

✅ Backports have been created

Details

• #7120 [9.4](backport #7119) build(deps): bump go.opentelemetry.io/otel from 1.43.0 to 1.44.0 has been created for branch 9.4
• #7121 [9.3](backport #7119) build(deps): bump go.opentelemetry.io/otel from 1.43.0 to 1.44.0 has been created for branch 9.3
• #7122 [8.19](backport #7119) build(deps): bump go.opentelemetry.io/otel from 1.43.0 to 1.44.0 has been created for branch 8.19 but encountered conflicts

Cherry-pick of a4c9ec3 has failed:

On branch mergify/bp/8.19/pr-7119
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit a4c9ec3.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   go.sum
	modified:   testing/go.mod
	modified:   testing/go.sum

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE-fips.txt
	both modified:   NOTICE.txt
	both modified:   go.mod

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally