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
Currently, indices store the agent.id and agent.groups fields along with the event information to build a relationship between an agent and its events.
However, we want to make more information available to correlate events from different indices. For example, the agent's information of an event would look like this:
Description
Currently, indices store the
agent.id
andagent.groups
fields along with the event information to build a relationship between an agent and its events.However, we want to make more information available to correlate events from different indices. For example, the agent's information of an event would look like this:
Aside from that, we also want to do some adjustments to the
.agents
index data model itself, which are:agent.is_connected
field toagent.status
, of typekeyword
. Expected values are:active
.disconnected
.Note
Take in consideration the requirements in #539, as all the Host fields must be included in the mappings.
Functional requirements
agents
index data model is updated with the changes above.Implementation restrictions
Host
fields underAgent
#539.Plan
agent.is_connected
field toagent.status
, of typekeyword
. Expected values are:active
.disconnected
.The text was updated successfully, but these errors were encountered: