[8.19](backport #7129) build(deps): bump github.com/elastic/elastic-agent-system-metrics from 0.14.3 to 0.14.4

[mergify]

Bumps github.com/elastic/elastic-agent-system-metrics from 0.14.3 to 0.14.4.

Release notes

Sourced from github.com/elastic/elastic-agent-system-metrics's releases.

v0.14.4

What's Changed

• Bump Golang version to 1.25.9 by @​ycombinator in elastic/elastic-agent-system-metrics#292
• Migrate from deprecated docker/docker to moby/moby modules by @​ycombinator in elastic/elastic-agent-system-metrics#291
• [cgv2] Convert cpu.stat microseconds to nanoseconds at parse site by @​orestisfl in elastic/elastic-agent-system-metrics#294

Full Changelog: elastic/elastic-agent-system-metrics@v0.14.3...v0.14.4

Commits

• 31d43a6 [cgv2] Convert cpu.stat microseconds to nanoseconds at parse site (#294)
• 2845450 Migrate from deprecated docker/docker to moby/moby modules (#291)
• 441a69b Bump Golang version to 1.25.9 (#292)
• See full diff 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)

---

This is an automatic backport of pull request #7129 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 565ea0f has failed:

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

You are currently cherry-picking commit 565ea0f.
  (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:   NOTICE-fips.txt
	modified:   NOTICE.txt
	modified:   go.mod

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.sum

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

[ebeahan]

@copilot fix the merge conflicts in this PR.

[Copilot]

@copilot fix the merge conflicts in this PR.

Resolved the go.sum merge conflict in commit fix: resolve go.sum merge conflict for backport to 8.19. The conflict was caused by a cherry-pick collision on go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp — the 8.19 branch had v0.53.0 while the backported commit introduced v0.60.0 (required by elastic-agent-system-metrics v0.14.4). Ran go mod tidy and go mod verify to confirm the go.sum is correct.

[ebeahan]

/test

[mergify]

This pull request is now in conflicts. Could you fix it @mergify[bot]? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.19/pr-7129 upstream/mergify/bp/8.19/pr-7129
git merge upstream/8.19
git push upstream mergify/bp/8.19/pr-7129

[github-actions]

TL;DR

Run check-ci failed because the PR’s module files are not tidy: mage check:ci runs go mod tidy -v, and that removes stale golang.org/x/mod and golang.org/x/tools indirect entries from go.mod/go.sum. This is dependency metadata drift, not a test flake.

Remediation

• Run go mod tidy on the PR branch and commit the resulting go.mod and go.sum changes.
• Re-run Buildkite Run check-ci (or locally run mage check:ci) to confirm no generated/tidy diff remains.

Investigation details

Root Cause

The failing commit 6589307997c344bee24a1ac4c508c3f7e0f9fcaa still includes these stale indirect module entries in go.mod:

	golang.org/x/mod v0.36.0 // indirect
	golang.org/x/tools v0.45.0 // indirect

mage check:ci invokes .buildkite/scripts/check_ci.sh, which runs mage check:ci. The relevant guard is Check.NoChanges in magefile.go:596-615: it runs go mod tidy -v, prints git diff, then fails if git update-index --refresh / git diff-index --exit-code HEAD -- sees changes. In the Buildkite log, go mod tidy produced a diff removing those stale entries and their checksums, so the no-changes guard failed.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/15198
• Job/step: Run check-ci / .buildkite/scripts/check_ci.sh
• Key log excerpt:

diff --git a/go.mod b/go.mod
@@ -93,10 +93,8 @@ require (
 	go.uber.org/multierr v1.11.0 // indirect
 	go.yaml.in/yaml/v2 v2.4.2 // indirect
 	golang.org/x/crypto v0.53.0 // indirect
-	golang.org/x/mod v0.36.0 // indirect
 	golang.org/x/sys v0.46.0 // indirect
 	golang.org/x/text v0.38.0 // indirect
-	golang.org/x/tools v0.45.0 // indirect

go.mod: needs update
go.sum: needs update
Error: git update-index failure: running "git update-index --refresh" failed with exit code 1

The same diff removes the matching golang.org/x/mod v0.36.0 and golang.org/x/tools v0.45.0 checksum lines from go.sum.

Verification

• Checked the failing Buildkite log and PR head module files.
• Checked for a matching open flaky-test issue; none found.
• Did not run the full check locally because this detective workflow is read-only and the CI log already shows the deterministic tidy diff.

---

What is this? | From workflow: PR Buildkite Detective

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

[mergify]

This pull request is now in conflicts. Could you fix it @mergify[bot]? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.19/pr-7129 upstream/mergify/bp/8.19/pr-7129
git merge upstream/8.19
git push upstream mergify/bp/8.19/pr-7129