[9.5](backport #52310) metricbeat/linux: align package metricsets with GA status

[mergify]

Proposed commit message

The Linux integration was released as GA, but Metricbeat still marked
its package-backed metricsets as beta in runtime warnings, field
metadata, and generated documentation.

Align the Linux module and the exposed system metricsets with the
package status. Keep pressure and RAPL beta for now because the package
does not expose them.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool. The GA release note was already published by the integrations package; this PR will use skip-changelog.

Disruptive User Impact

None.

How to test this PR locally

N/A

Related issues

• Follows feat(linux): Release linux metrics package as GA integrations#15658

---

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

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• /test : Run the Buildkite pipeline.

[infra-vault-gh-plugin-prod]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[github-actions]

🔍 Preview links for changed docs

• docs/reference/metricbeat/exported-fields-linux.md
• docs/reference/metricbeat/exported-fields-system.md
• docs/reference/metricbeat/metricbeat-metricset-linux-conntrack.md
• docs/reference/metricbeat/metricbeat-metricset-linux-iostat.md
• docs/reference/metricbeat/metricbeat-metricset-linux-ksm.md
• docs/reference/metricbeat/metricbeat-metricset-linux-memory.md
• docs/reference/metricbeat/metricbeat-metricset-linux-pageinfo.md
• docs/reference/metricbeat/metricbeat-metricset-system-network_summary.md
• docs/reference/metricbeat/metricbeat-metricset-system-service.md
• docs/reference/metricbeat/metricbeat-metricset-system-users.md

More links …

• docs/reference/metricbeat/metricbeat-module-linux.md
• docs/reference/metricbeat/metricbeat-module-system.md
• docs/reference/metricbeat/metricbeat-modules.md
• metricbeat/module/linux/_meta/docs.md
• metricbeat/module/linux/conntrack/_meta/docs.md
• metricbeat/module/linux/iostat/_meta/docs.md
• metricbeat/module/linux/ksm/_meta/docs.md
• metricbeat/module/linux/memory/_meta/docs.md
• metricbeat/module/linux/pageinfo/_meta/docs.md
• metricbeat/module/system/network_summary/_meta/docs.md
• metricbeat/module/system/service/_meta/docs.md
• metricbeat/module/system/users/_meta/docs.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

TL;DR

Buildkite failed in x-pack/metricbeat: Go Integration Tests (Module) because the cockroachdb module test run failed, but the top-level step log only shows the module summary (failed modules: cockroachdb) and not the underlying test error. Immediate next step is to re-run that job and inspect the TEST-go-integration-cockroachdb.out.json artifact for the first failing test/event.

Remediation

• Re-run the failed Buildkite job (:ubuntu: x-pack/metricbeat: Go Integration Tests (Module)) to rule out transient infra/container startup issues.
• In the rerun (or this run’s artifacts), open x-pack/metricbeat/build/TEST-go-integration-cockroachdb.out.json and identify the first Action:"fail"/panic event; that event should pinpoint the exact failing package/test.
• If the failure is around service startup/connection, focus on x-pack/metricbeat/module/cockroachdb/status/status_integration_test.go:32 (compose.EnsureUp(t, "cockroachdb")) and the CockroachDB compose service used by that module.

Investigation details

Root Cause

From the provided failing step log, the directly observable failure is module-level:

• /tmp/gh-aw/buildkite-logs/beats-xpack-metricbeat-ubuntu-x-packmetricbeat-go-integration-tests-module.txt:17 → Error: failed modules: cockroachdb

The mage runner emits this summary after collecting per-module errors:

• dev-tools/mage/gotest.go:341-350 prints module failures and returns fmt.Errorf("failed modules: %s", ...).

So the root cause is inside the cockroachdb module integration test output, but that detailed error is not present in the provided top-level Buildkite log excerpt.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/51357
• Job/step: :ubuntu: x-pack/metricbeat: Go Integration Tests (Module)
• Key log excerpt:
  • /tmp/gh-aw/buildkite-logs/beats-xpack-metricbeat-ubuntu-x-packmetricbeat-go-integration-tests-module.txt:17
    • Error: failed modules: cockroachdb

Verification

• Not run locally (this detective workflow is read-only and the required module integration environment is Buildkite-managed).

Follow-up

• If rerun reproduces, share the first failing event from TEST-go-integration-cockroachdb.out.json; that will allow a precise code-level fix recommendation instead of module-level triage.

---

What is this? | From workflow: PR Buildkite Detective

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