Add per_user services filter to windows_service

[clarkb7]

What does this PR do?

Adds a per_user boolean criterion to the windows_service services filter, mirroring the existing trigger_start criterion. A filter item can match services by whether they are Windows per-user service instances (named <template>_<LUID>, e.g. OneSyncSvc_443f50). To exclude per-user services from collection, configure per_user: false to collect only non-per-user services:

services:
  - per_user: false

per_user composes with name, startup_type, and trigger_start in any filter item. When group_per_user_services is enabled alongside a per_user: false filter, a warning is logged since excluded services are never collected and cannot be grouped.

Motivation

Per-user services are often pure noise on monitored hosts, and each carries a per-session/per-host LUID suffix that inflates windows_service tag cardinality. This complements the group_per_user_services option (parent PR) by letting users drop per-user services from collection entirely rather than grouping them.

Stacked on #24087 — this PR targets branden.clark/windows-service-group-per-user and should be reviewed/merged after it.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[datadog-prod-us1-4]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 95.27% (+7.27%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: a1ef409 | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

The backport to 7.80.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-7.80.x 7.80.x
# Navigate to the new working tree
cd .worktrees/backport-7.80.x
# Create a new branch
git switch --create backport-24088-to-7.80.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3ca0f7de0a36adad7275e9761b189bda21c41524
# Push it to GitHub
git push --set-upstream origin backport-24088-to-7.80.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-7.80.x

Then, create a pull request where the base branch is 7.80.x and the compare/head branch is backport-24088-to-7.80.x.

[dd-octo-sts]

The backport to 7.81.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-7.81.x 7.81.x
# Navigate to the new working tree
cd .worktrees/backport-7.81.x
# Create a new branch
git switch --create backport-24088-to-7.81.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3ca0f7de0a36adad7275e9761b189bda21c41524
# Push it to GitHub
git push --set-upstream origin backport-24088-to-7.81.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-7.81.x

Then, create a pull request where the base branch is 7.81.x and the compare/head branch is backport-24088-to-7.81.x.

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run