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
In mappings for .fleet-agents index, it seems like not all fields we define are actually used when ES documents are written with agent information. For example the mappings define fields like agent, packages, last_updated (updated_at is used, however), last_checkin_status, but they don't appear on the ES documents.
Can we do an audit and get rid of unnecessary mappings?
Currently the UX impact is that these unused fields are showing up in the autocomplete search bar in Kibana: elastic/kibana#100391 (comment)
I believe last_checkin_status was accidental omission. It is used in AgentService.getAgentStatus which is used in the Agent list and detail views, as well as a few agent API endpoints.
In mappings for
.fleet-agents
index, it seems like not all fields we define are actually used when ES documents are written with agent information. For example the mappings define fields likeagent
,packages
,last_updated
(updated_at
is used, however),last_checkin_status
, but they don't appear on the ES documents.Can we do an audit and get rid of unnecessary mappings?
Currently the UX impact is that these unused fields are showing up in the autocomplete search bar in Kibana: elastic/kibana#100391 (comment)
The text was updated successfully, but these errors were encountered: