# Endpoint does not show up in Asset management page

**URL:** <https://discuss.elastic.co/t/endpoint-does-not-show-up-in-asset-management-page/387505>\
**Category:** Endpoint Security\
**Created:** [July 3, 2026, 2:46pm UTC](https://discuss.elastic.co/t/endpoint-does-not-show-up-in-asset-management-page/387505 "2026-07-03T14:46:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**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 3, 2026, 2:46pm UTC](https://discuss.elastic.co/t/endpoint-does-not-show-up-in-asset-management-page/387505/1 "2026-07-03T14:46:39Z")

</div>

Hello,

I have a deployment on Elastic Cloud for tests and I'm doing a test with Elastic Defend.

I have a policy that has Elastic Defend configured with 1 agent enrolled with healthy status.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/b/7bfbf376016e6fb0935298d52735efd0c0627dc6.png)

But when I go into Assets \> Endpoint, I'm being asked to Enroll an Agent.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/0/3095463227deb8d01ce40ea947954a4482818e38.png)

Going into Assets \> Policies, I can see the policie and it says that there is one Endpoint:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/2/92e304e9ee90651737e534e183af0ee6ff5be190.png)

But once I click in the policy, it shows that there is 0 agents.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/2/b204c453a964df9bf948262a6e242ba9275d8b3d.png)

This seems a bug to me, am I missing something?

---

<div class="post-metadata">

**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 3, 2026, 4:18pm UTC](https://discuss.elastic.co/t/endpoint-does-not-show-up-in-asset-management-page/387505/2 "2026-07-03T16:18:59Z")

</div>

Clicking on the policy page, it seems to make a request to the following endpoint:

```auto
https://kibana-endpoint/api/fleet/agent_status?policyId=2e2baf43-777d-4583-8d3f-8b4778d80c6a

```

Where `2e2baf43-777d-4583-8d3f-8b4778d80c6a` is the current policy id.

Running the same request in Dev Tools, it returns this:

```auto
{
  "results": {
    "online": 0,
    "error": 0,
    "inactive": 0,
    "offline": 0,
    "updating": 0,
    "unenrolled": 0,
    "orphaned": 0,
    "uninstalled": 0,
    "all": 0,
    "active": 0,
    "other": 0,
    "events": 0
  }
}

```

But, there is an agent on this policy:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/5/0597626ed0b4dcfac4d8cced4b9529bfec8f0e03.png)

---

<div class="post-metadata">

**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 3, 2026, 4:30pm UTC](https://discuss.elastic.co/t/endpoint-does-not-show-up-in-asset-management-page/387505/3 "2026-07-03T16:30:11Z")

</div>

Well, it seems a bug.

While getting information from the agent with `GET kbn:/api/fleet/agents/35486eb6-f886-4d2a-9ecd-c82a833968b2` the relevante response is:

```auto
{
  "item": {
    "id": "35486eb6-f886-4d2a-9ecd-c82a833968b2",
    "type": "PERMANENT",
    "namespaces": [
      "default"
    ],
    "active": true,
    "enrolled_at": "2026-05-13T01:36:06Z",
    "upgraded_at": "2026-07-03T00:48:04Z",
    "upgrade_started_at": null,
    "upgrade_details": null,
    "access_api_key_id": "37n6Hp4BhFyRaqMrEwWq",
    "policy_id": "2e2baf43-777d-4583-8d3f-8b4778d80c6a#9.4",
    "last_checkin": "2026-07-03T16:26:10Z",
    "last_checkin_status": "online",
    "last_checkin_message": "Running",
    "policy_revision": 30,

```

The policy id returned is the versioned policy id, in this case `2e2baf43-777d-4583-8d3f-8b4778d80c6a#9.4`

The request made by the Kibana UI uses the policy id `2e2baf43-777d-4583-8d3f-8b4778d80c6a` without the version, I'm not sure the endpoint used supports wildcard.

If I made the same request using the policy id, I will have the expected information.

This is the request made by the Assets \> Endpoints \> Policies UI

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/8/a8dafb19f53eb2a152e8cc7e2011495d673fd491.png)

Adding the versioned policy (escaping the #), I get results:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/1/61e3e51d576011373c518b410cf4bb51c7a47b48.png)

---

<div class="post-metadata">

**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 3, 2026, 6:51pm UTC](https://discuss.elastic.co/t/endpoint-does-not-show-up-in-asset-management-page/387505/4 "2026-07-03T18:51:03Z")

</div>

Opened 2 issues about this:

> <https://github.com/elastic/kibana/issues/276294>
>
> Hello,
> 
> Some integration packages and inputs now may require minimum Elastic Age…nt version, this will lead to the creation of Version-specific agent policies according to this \[documentation\](https://www.elastic.co/docs/reference/fleet/version-specific-agent-policies).
> 
> If a policy \*\*does not have\*\* any integration or input package that has a minimum required agent version, the agents will report that their policy id as the policy id defined in fleet, for example:
> 
> \`\`\`
> "policy\_id": "2e2baf43-777d-4583-8d3f-8b4778d80c6a"
> \`\`\`
> 
> If there is a package or input that would lead to a version-specific policy, the agents will report their policy id with their version \`major.minor\` added to the end, like:
> 
> \`\`\`
> "policy\_id": "2e2baf43-777d-4583-8d3f-8b4778d80c6a#9.4"
> \`\`\`
> 
> Last month we opened a support ticket because some agents stopped syncing the changes on the policies and this was impacting on the management of the agents, this lead to this PR #273122, which aimed to fix this issue.
> 
> Before upgrading I've decided to validate the fix on a lab deployment and this issue may still happen in some cases.
> 
> If the agent policy \*\*already has\*\* an integration package or input that would lead to version-specific policies, it seems that the PR fixed the previous issue and agents on specific version will now sync to the last version of the policy and also subsequent changes
> 
> If the agent policy \*\*does not have yet\*\* an integration package or input that would lead to version-specific policies, this will trigger the creation of these policies and the agents would also sync for the last version and subsequent changes.
> 
> But if you remove the integration or input that requires version-specific policies, the agent will then revert to reporting the policy id without the version number and will stop syncing, it will be in an \*outdated policy\* state from now on.
> 
> To make the agent sync you would need to add back an integration/input that would trigger a version-specific policy or move it to another policy and then move it back to its correct policy.
> 
> \### How to replicate
> 
> On a 9.4.3 deployment create a policy \*\*without\*\* any integration package or input that requires version-specific policy.
> 
> I've used these ones:
> 
> \<img width="2166" height="360" alt="Image" src="https://github.com/user-attachments/assets/882219fb-7f9f-49c3-9a1f-a691f11fc763" /\>
> 
> Enroll an agent on this policy and check what is the \`policy\_id\` it reports by running \`GET kbn:/api/fleet/agents/AGENT\_ID\` in Kibana Dev Tools, example response:
> 
> \`\`\`
> {
> "item": {
> "id": "35486eb6-f886-4d2a-9ecd-c82a833968b2",
> "type": "PERMANENT",
> "namespaces": \[
> "default"
> \],
> "active": true,
> "enrolled\_at": "2026-05-13T01:36:06Z",
> "upgraded\_at": "2026-07-03T00:48:04Z",
> "upgrade\_started\_at": null,
> "upgrade\_details": null,
> "access\_api\_key\_id": "37n6Hp4BhFyRaqMrEwWq",
> "policy\_id": "2e2baf43-777d-4583-8d3f-8b4778d80c6a",
> "last\_checkin": "2026-07-03T18:20:28Z",
> "last\_checkin\_status": "online",
> "last\_checkin\_message": "Running",
> "policy\_revision": 42,
> \`\`\`
> 
> Make some changes in some of the integration or policy, like changing the description, to increase the revision and validate that the agent is syncing in the Fleet UI.
> 
> After that add an integration that will require a version-specific agent policy, for this I'm using the \*Auditd\* integration.
> 
> \<img width="2169" height="426" alt="Image" src="https://github.com/user-attachments/assets/a1f33ca8-f302-441f-bb7b-125f62339c76" /\>
> 
> Validate in the Fleet UI that the agent sync with the last version, change the description of the policy to see that it stills sync with the last version.
> 
> Repeat the \`GET kbn:/api/fleet/agents/AGENT\_ID\` request and the policy\_id reported now has an specific-version:
> 
> \`\`\`
> {
> "item": {
> "id": "35486eb6-f886-4d2a-9ecd-c82a833968b2",
> "type": "PERMANENT",
> "namespaces": \[
> "default"
> \],
> "active": true,
> "enrolled\_at": "2026-05-13T01:36:06Z",
> "upgraded\_at": "2026-07-03T00:48:04Z",
> "upgrade\_started\_at": null,
> "upgrade\_details": null,
> "access\_api\_key\_id": "37n6Hp4BhFyRaqMrEwWq",
> "policy\_id": "2e2baf43-777d-4583-8d3f-8b4778d80c6a#9.4",
> "last\_checkin": "2026-07-03T18:26:59Z",
> "last\_checkin\_status": "online",
> "last\_checkin\_message": "Running",
> "policy\_revision": 46,
> \`\`\`
> 
> Remove the \*Auditd\* integration from the policy and new the issue happens, the agent will be in an \*outdated policy\* state and will not sync any changes anymore.
> 
> It will still report the policy\_id with the specific version if you check the API, but this is not its correct policy anymore as none of the integrations in the policy requires it.
> 
> \<img width="1987" height="160" alt="Image" src="https://github.com/user-attachments/assets/dd33ecf2-1589-4028-9cb5-3c18101d04e4" /\>

and

> <https://github.com/elastic/kibana/issues/276295>
>
> Hello,
> 
> Some Elastic Agent integrations packages and Inputs now can lead to the …creation of an Version-specific policy, if a version-specific policy also has the Elastic Defend integration, those agents will not show up in the \*Assets \> Endpoints\* and \*Assets \> Endpoints \> Policies\* pages.
> 
> Agents on version-specic policies report their policy\_id with their version in the end:
> 
> \`\`\`
> "policy\_id": "2e2baf43-777d-4583-8d3f-8b4778d80c6a#9.4"
> \`\`\`
> 
> It seems that neither of those Asset pages can work if the policy id is reported like this, for example the \*Assets \> Endpoints \> Policies\* makes a request to the Kibana API agent\_status endpoint in this way:
> 
> \`\`\`
> /api/fleet/agent\_status?policyId=2e2baf43-777d-4583-8d3f-8b4778d80c6a
> \`\`\`
> No agents will be reported since this policy is now version-specific and will have a derived policy for each agent \`major.minor\` version.
> 
> This seems to be reletated to this issue I've just opened: #276294 
> 
> I've also created a discuss topic with some evidences \[here\](https://discuss.elastic.co/t/endpoint-does-not-show-up-in-asset-management-page/387505).
> 
> This is all on version 9.4.3 on a cloud deployment.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 31, 2026, 6:51pm UTC](https://discuss.elastic.co/t/endpoint-does-not-show-up-in-asset-management-page/387505/5 "2026-07-31T18:51:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.