# /app/fleet/agents shows no agents in Kibana, but API does **URL:** \ **Category:** Kibana\ **Created:** [July 15, 2026, 3:04pm UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372 "2026-07-15T15:04:56Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![leprovokateur](https://avatars.discourse-cdn.com/v4/letter/l/8e8cbc/32.png) [@leprovokateur](https://discuss.elastic.co/u/leprovokateur)\ **Post date:** [July 15, 2026, 3:04pm UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372/1 "2026-07-15T15:04:56Z")
Hi, I use elastic stack in version 9.4.3. I have one fleet instance running, but it's not visible in the Kibana UI: ![2026-07-15 17_03_19-Clipboard](https://us1.discourse-cdn.com/elastic/original/3X/e/4/e44743678b4d7bfbc311d4b1e3390a5e8c4d1d75.png) An API call via curl shows otherwise: `{` `"items": [` `{` `"id": "3b28b7af-6b94-4a08-8105-5ba0b25afd3e",` `"type": "PERMANENT",` `"namespaces": [` `"default"` `],` `"active": true,` `"enrolled_at": "2026-07-15T14:07:48Z",` `"access_api_key_id": "xxx",` `"policy_id": "fleet-server-policy#9.4",` `"last_checkin": "2026-07-15T14:29:22Z",` `"last_checkin_status": "online",` `"last_checkin_message": "Running",` `"policy_revision": 4,` `"sequence_num": 0,` `"status": "online"` `}` I see two errors in the browser console: > 1. Content Security Policy blocks inline execution of scripts and stylesheets > 1. The Content Security Policy (CSP) prevents cross-site scripting attacks by blocking inline execution of scripts and style sheets. > > 2. > 1. **2 directives** > 1. > > | **Directive** | **Element** | **Source location** | **Status** | > | --- | --- | --- | --- | > | **script-src-elem** | | **agents:187** | **blocked** | > | **script-src-elem** | | **agents:187** | **report-only** | > 1. > - Learn more: Content Security Policy - Inline Code > > 2. Content Security Policy of your site blocks the use of 'eval' in JavaScript` > 1. The Content Security Policy (CSP) prevents the evaluation of arbitrary strings as JavaScript to make it more difficult for an attacker to inject unathorized code on your site. > > 2. > 1. **2 directives** > 1. > > | **Source location** | **Directive** | **Status** | > | --- | --- | --- | > | **kbn-ui-shared-deps-npm.dll.js:456** | **script-src** | **blocked** | > | **kbn-ui-shared-deps-npm.dll.js:456** | **script-src** | **report-only** | What can I do? Best regards, Robert ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 15, 2026, 3:14pm UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372/2 "2026-07-15T15:14:10Z")
What integrations do you have in the policy: `fleet-server-policy` ? ---
**Author:** ![leprovokateur](https://avatars.discourse-cdn.com/v4/letter/l/8e8cbc/32.png) [@leprovokateur](https://discuss.elastic.co/u/leprovokateur)\ **Post date:** [July 15, 2026, 8:04pm UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372/3 "2026-07-15T20:04:24Z")
Hi Leandro, I have auditd-6 Auditd Logs v3.23.0 fleet\_server-1 Fleet Server v1.6.1 system-logs-metrics-fleet System v2.21.0 ---
**Author:** ![leprovokateur](https://avatars.discourse-cdn.com/v4/letter/l/8e8cbc/32.png) [@leprovokateur](https://discuss.elastic.co/u/leprovokateur)\ **Post date:** [July 15, 2026, 8:26pm UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372/4 "2026-07-15T20:26:55Z")
Hi Leandro, After I deleted the fleet server policy and uninstalled the corresponding agent, I reinstalled the agent and could see the agent in the fleet agent overview. Then I edited the policy and added an auditd integration, which made the agent disappear from the overview. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 15, 2026, 8:31pm UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372/5 "2026-07-15T20:31:59Z")
Was this Github issue created by you? > > > \## Kibana versions > > \\\>=9.3.1 > > \## Describe the bug > > When the \`fleet:version-speci…fic-policy-assignment-task\` reassigns a Fleet Server agent from its base policy ID (e.g. fleet-server-policy) to a version-specific ID (e.g. fleet-server-policy#9.4), the Fleet Agents page permanently shows the "Add a Fleet Server" onboarding screen even though the Fleet Server agent is online and healthy. > > \## Root cause > > \`hasFleetServersForPolicies\` in \`fleet\_server/index.ts:79\` constructs an exact-match KQL filter against \`.fleet-agents\`: > > \`\`\` > return \`(policy\_id:"${escapeQuotes(id)}" and (${space}))\`; > \`\`\` > > This matches \`policy\_id:"fleet-server-policy"\` but not \`policy\_id:"fleet-server-policy#9.4"\`. Once the assignment task runs, zero agents match the query, \`hasFleetServers()\` > returns false, and \`GET /api/fleet/agents/setup\` returns \`isReady: false, missing\_requirements: \["fleet\_server"\]\` which triggers the onboarding screen in Fleet > > \## Steps to reproduce > > 1. Create a Fleet Server agent policy that includes any integration whose agent stream template contains a \`{{#semverSatisfies \_meta.agent.version ...}}\` block (e.g. > auditd ≥ 3.23.0)) > 2. Enroll a Fleet Server agent into that policy > 3. Wait for \`fleet:version-specific-policy-assignment-task\` to run (default interval: 1 minute) > 4. Navigate to Fleet → Agents — the "Add a Fleet Server" onboarding screen appears despite the Fleet Server agent being online > > \## Expected behavior > > The Fleet Agents page shows the agent list normally. \`GET /api/fleet/agents/setup\` returns \`isReady: true\`. > [@leprovokateur](#): > > Then I edited the policy and added an auditd integration, which made the agent disappear from the overview. This is the problem, there is a current issue in Kibana related to version-specific agent policies, if an Agent Policy has an integration that will lead to the creation of version-specific policies, this may have some impact in some places. The `Auditd` integration is one of the integrations that will lead to the creation of version-specific policies. Until this is fixed in Kibana you need to remove the `Auditd` integration for things work well. ---
**Author:** ![leprovokateur](https://avatars.discourse-cdn.com/v4/letter/l/8e8cbc/32.png) [@leprovokateur](https://discuss.elastic.co/u/leprovokateur)\ **Post date:** [July 15, 2026, 8:40pm UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372/6 "2026-07-15T20:40:03Z")
Hi Leandro, I didn't create the github issue. Can you tell which exact version of Kibana introduced this behavior? ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 15, 2026, 9:01pm UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372/7 "2026-07-15T21:01:56Z")
> [@leprovokateur](#): > > I didn't create the github issue. No problem, but it seems to be exactly the same issue. > [@leprovokateur](#): > > Can you tell which exact version of Kibana introduced this behavior? Version specific agent policies were introduced in version 9.4 ---
**Author:** ![leprovokateur](https://avatars.discourse-cdn.com/v4/letter/l/8e8cbc/32.png) [@leprovokateur](https://discuss.elastic.co/u/leprovokateur)\ **Post date:** [August 13, 2026, 11:48am UTC](https://discuss.elastic.co/t/app-fleet-agents-shows-no-agents-in-kibana-but-api-does/388372/9 "2026-08-13T11:48:22Z")
The issues seems to be solved in the latest versions of kibana.