Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jan 20, 2026

Proposed commit message

See title

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.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

On Linux
Screenshot 2026-01-07 at 15 48 30

Some validation of the output
Screenshot 2026-01-07 at 16 10 27

As is visible on the screenshot process with PID 43 and 90 really used no swap memory. And process with PID 640 used 1272 kB of swap memory (which is 1302528 bytes) and it matches what is shown in Kibana.

To make sure nothing breaks on other platforms I've run a test on macos (it is working fine, swap field is null on other than Linux platforms)
Screenshot 2026-01-08 at 11 26 04

Logs


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

#48334)

* [metricbeat][system] add swap field to system.process.memory metricset

* update docs

* update NOTICE.txt

* remove field mapping

* make changelog message more accurate

* revert removing of field mapping

* resolve PR comment

* Update metricbeat/module/system/process/_meta/fields.yml

Co-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>

* make update

* update swap field ga version

---------

Co-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>
(cherry picked from commit 90844ec)

# Conflicts:
#	NOTICE.txt
#	docs/reference/metricbeat/exported-fields-system.md
#	docs/reference/metricbeat/metricbeat-metricset-system-process.md
#	go.mod
#	go.sum
#	metricbeat/module/system/fields.go
@mergify mergify bot requested a review from a team as a code owner January 20, 2026 17:11
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Jan 20, 2026
@mergify mergify bot requested review from a team as code owners January 20, 2026 17:11
@mergify mergify bot requested review from VihasMakwana and andrzej-stencel and removed request for a team January 20, 2026 17:11
@mergify
Copy link
Contributor Author

mergify bot commented Jan 20, 2026

Cherry-pick of 90844ec has failed:

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

You are currently cherry-picking commit 90844ec02.
  (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:
	new file:   changelog/fragments/1767864511-add-swap-field-to-system.process.memory-metric-set-in-metricbeats.yaml
	modified:   metricbeat/module/system/process/_meta/data.json
	modified:   metricbeat/module/system/process/_meta/fields.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   NOTICE.txt
	deleted by us:   docs/reference/metricbeat/exported-fields-system.md
	deleted by us:   docs/reference/metricbeat/metricbeat-metricset-system-process.md
	both modified:   go.mod
	both modified:   go.sum
	both modified:   metricbeat/module/system/fields.go

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

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 20, 2026
@github-actions
Copy link
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@github-actions github-actions bot added enhancement Metricbeat Metricbeat Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team labels Jan 20, 2026
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport conflicts There is a conflict in the backported pull request enhancement Metricbeat Metricbeat Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants