Skip to content

Comments

[8.19](backport #48644) [perfmon/windows] - Add the ability to extract object names from counters#48882

Open
mergify[bot] wants to merge 1 commit into8.19from
mergify/bp/8.19/pr-48644
Open

[8.19](backport #48644) [perfmon/windows] - Add the ability to extract object names from counters#48882
mergify[bot] wants to merge 1 commit into8.19from
mergify/bp/8.19/pr-48644

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Feb 17, 2026

Proposed commit message

When using wildcards for perfmon objects in the windows Integration, the windows.perfmon.object field should show the actual object name, not the wildcard

Previously, when using wildcards for Perfmon objects in the Windows Integration, the windows.perfmon.object field would retain the wildcard instead of reporting the actual object name.
For example, given the following Perfmon objects:

sql_server1:Databases
Sql_testServer:Databases
SomeOtherSQLVersion:Databases

and the following Perfmon collection configuration:

object: "*:Databases"
instance: ["*"]
counters:
  - name: "Transactions/sec"

all instances from all databases are discovered and reported. However, the windows.perfmon.object field would show *:Databases instead of the real object names such as sql_server1:Databases.

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

Logs


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

…ters (#48644)

* initial commit

* add tests

* changelog

* docs

* lint

* unset

* doc

* docs

* fix unit tests

* enhance regex

* Update metricbeat/module/windows/perfmon/_meta/docs.md

Co-authored-by: Janeen Mikell Roberts <57149392+jmikell821@users.noreply.github.com>

* Update docs/reference/metricbeat/metricbeat-metricset-windows-perfmon.md

Co-authored-by: Janeen Mikell Roberts <57149392+jmikell821@users.noreply.github.com>

---------

Co-authored-by: Janeen Mikell Roberts <57149392+jmikell821@users.noreply.github.com>
(cherry picked from commit 4a1bba9)
@mergify mergify bot added the backport label Feb 17, 2026
@mergify mergify bot requested review from a team as code owners February 17, 2026 06:45
@mergify mergify bot requested review from faec and leehinman and removed request for a team February 17, 2026 06:45
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 17, 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 Team:Docs Label for the Observability docs team Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Feb 17, 2026
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Feb 17, 2026
@elasticmachine
Copy link
Contributor

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

@github-actions
Copy link
Contributor

✅ Vale Linting Results

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.

@VihasMakwana
Copy link
Contributor

@copilot Review this PR for me.

Copy link

Copilot AI commented Feb 22, 2026

@VihasMakwana I've opened a new pull request, #49034, to work on those changes. Once the pull request is ready, I'll request review from you.

@mergify
Copy link
Contributor Author

mergify bot commented Feb 23, 2026

This pull request has not been merged yet. Could you please review and merge it @VihasMakwana? 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Team:Docs Label for the Observability docs team Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants