You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Elastic Agent]: Navigation from the "Agent Info Metrics" link in Fleet applies filter that hides data #18941
tl;dr: The strongest evidence points to a package-side filter regression introduced in #18251: the Overview dashboard now defaults to host.os.type (existsSelected: true), which can exclude most docs for agents/data where host.os.type is not populated/mapped the way host.os.family was.
Recommendation
Treat this as a likely regression from the OS filter migration in #18251, and patch the Overview dashboard to avoid a hard default on host.os.type for entry navigation. The safest fix is to remove the default existsSelected constraint on the Platform control and update OS panels to support both legacy and new field/value shapes during transition.
Findings
#18251 explicitly changed Overview filters from host.os.family to host.os.type and darwin to macos.
packages/elastic_agent/changelog.yml:12-16
Commit diff in repo history: dc20b4c88
packages/elastic_agent/kibana/dashboard/elastic_agent-a148dc70-6b3c-11ed-98de-67bdecd21824.json:32 now uses "fieldName": "host.os.type" with "existsSelected": true.
The Overview dashboard has hard app-state filters that can narrow data significantly.
packages/elastic_agent/kibana/dashboard/elastic_agent-a148dc70-6b3c-11ed-98de-67bdecd21824.json:393-419 (platform filters on host.os.type, values macos/windows)
...:586-598 (host.os.type: macos)
...:762-774 (host.os.type: windows)
Package field definitions across data streams still consistently declare host.os.family in agent.yml, while no host.os.type declarations were found in package data stream field files.
Same pattern appears broadly under packages/elastic_agent/data_stream/**/fields/agent.yml.
Related but secondary: 2.8.0 also changed dashboard navigation links (#18410), so it is related context but not the strongest direct root-cause signal for this symptom.
packages/elastic_agent/changelog.yml:2-6
Verification
I validated the regression point and current asset state from repo history and package assets:
$ git --no-pager log --oneline -- packages/elastic_agent/kibana/dashboard/elastic_agent-a148dc70-6b3c-11ed-98de-67bdecd21824.json | head -n 4
e322c1ce1 Correct dashboard links (#18410)
dc20b4c88 [elastic_agent] Fix OS type counts in Overview dashboard to use host.os.type (#18251)
dcffec345 [elastic_agent] Add 10 remaining input dashboards (#14690)
bc923e680 [CI] [Backports] Ensure all expected entries are removed in CODEOWNERS file (#14012)
$ git --no-pager show --oneline dc20b4c88 -- packages/elastic_agent/kibana/dashboard/elastic_agent-a148dc70-6b3c-11ed-98de-67bdecd21824.json
@@ -29,7 +29,7 @@
- "fieldName": "host.os.family",
+ "fieldName": "host.os.type",
@@
- "host.os.family": "darwin"
+ "host.os.type": "macos"
And current file inspection confirms host.os.type + default exists behavior in the shipped 2.8.0 asset.
Remove default platform hard-filtering (existsSelected: true on host.os.type) so landing via Fleet doesn’t pre-hide data.
Make OS panel filters backward-compatible:
Replace strict host.os.type-only filters with combined logic supporting both old/new shapes (e.g., host.os.type: macos OR host.os.family: darwin, similar for windows/linux derivation).
Keep Fleet navigation behavior unchanged initially; validate by opening the same Fleet “Agent Info Metrics” path and confirming charts populate.
Add a changelog.yml bugfix entry in packages/elastic_agent/changelog.yml referencing this issue.
Backport as needed to supported branches where package versions include #18251 behavior.
changed the title [-][IElastic Agent]: Navigation from the "Agent Info Metrics" link in Fleet applies filter that hides data[/-][+][Elastic Agent]: Navigation from the "Agent Info Metrics" link in Fleet applies filter that hides data[/+]on May 21, 2026
Activity
infra-vault-gh-plugin-prod commentedon May 11, 2026
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)
cmacknz commentedon May 11, 2026
Suspicion is that #18251 broke this accidentally FYI @mauri870 since you were the author of that PR.
github-actions commentedon May 11, 2026
tl;dr: The strongest evidence points to a package-side filter regression introduced in
#18251: the Overview dashboard now defaults tohost.os.type(existsSelected: true), which can exclude most docs for agents/data wherehost.os.typeis not populated/mapped the wayhost.os.familywas.Recommendation
Treat this as a likely regression from the OS filter migration in
#18251, and patch the Overview dashboard to avoid a hard default onhost.os.typefor entry navigation. The safest fix is to remove the defaultexistsSelectedconstraint on the Platform control and update OS panels to support both legacy and new field/value shapes during transition.Findings
#18251explicitly changed Overview filters fromhost.os.familytohost.os.typeanddarwintomacos.packages/elastic_agent/changelog.yml:12-16dc20b4c88packages/elastic_agent/kibana/dashboard/elastic_agent-a148dc70-6b3c-11ed-98de-67bdecd21824.json:32now uses"fieldName": "host.os.type"with"existsSelected": true.packages/elastic_agent/kibana/dashboard/elastic_agent-a148dc70-6b3c-11ed-98de-67bdecd21824.json:393-419(platform filters onhost.os.type, valuesmacos/windows)...:586-598(host.os.type: macos)...:762-774(host.os.type: windows)host.os.familyinagent.yml, while nohost.os.typedeclarations were found in package data stream field files.packages/elastic_agent/data_stream/elastic_agent_metrics/fields/agent.yml:51(- name: os.family)packages/elastic_agent/data_stream/**/fields/agent.yml.#18410), so it is related context but not the strongest direct root-cause signal for this symptom.packages/elastic_agent/changelog.yml:2-6Verification
I validated the regression point and current asset state from repo history and package assets:
And current file inspection confirms
host.os.type+ default exists behavior in the shipped 2.8.0 asset.Detailed Action Plan
packages/elastic_agent/kibana/dashboard/elastic_agent-a148dc70-6b3c-11ed-98de-67bdecd21824.json:existsSelected: trueonhost.os.type) so landing via Fleet doesn’t pre-hide data.host.os.type-only filters with combined logic supporting both old/new shapes (e.g.,host.os.type: macos OR host.os.family: darwin, similar for windows/linux derivation).changelog.ymlbugfix entry inpackages/elastic_agent/changelog.ymlreferencing this issue.#18251behavior.Related Items
host.os.family→host.os.typedashboard filter changespackages/elastic_agent/kibana/dashboard/elastic_agent-a148dc70-6b3c-11ed-98de-67bdecd21824.jsonpackages/elastic_agent/data_stream/elastic_agent_metrics/fields/agent.ymlos.familyfield usage in package field declarationspackages/elastic_agent/changelog.ymlNote
🔒 Integrity filter blocked 4 items
The following items were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Issue Triage
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Danouchka commentedon May 21, 2026
+1
mauri870 commentedon May 21, 2026
Apologies, missed this on my inbox. Very likely that #18251 broke it.
Investigating.
[-][IElastic Agent]: Navigation from the "Agent Info Metrics" link in Fleet applies filter that hides data[/-][+][Elastic Agent]: Navigation from the "Agent Info Metrics" link in Fleet applies filter that hides data[/+]elastic-vault-github-plugin-prod commentedon May 21, 2026
Package elastic_agent - 2.9.1 containing this change is available at https://epr.elastic.co/package/elastic_agent/2.9.1/