[Ingest] Fleet agent details UI

[jen-huang]

View in Figma

Add "Activity Log" and "Agent details" tabs to the agent detail page.

[elasticmachine]

Pinging @elastic/ingest (Feature:Fleet)

[mostlyjason]

@ruflin It looks like a timestamped event history, so what makes it different than a log?

[ruflin]

@mostlyjason You are correct, it is a log entry. I assume the point you are getting at, should this be stored as saved object or not?

[mostlyjason]

Yes it seems like if its a saved object you don't get search, dashboards, alerts, ILM and everything else we've built to make logs a great experience. What is the advantage of using a saved object? Seems like you'd have to replicate a lot of those pieces manually like deleting old data, etc.

[ruflin]

@mostlyjason +1 on thinking of this as data. I even remember a chat I had with @nchaulet and @ph where we came to the same conclusion. The only advantage of saved objects here would be to have it space aware, but I don't think this is the key here.

[ph]

@ruflin without being a saved object this would mean that you could access logs of any agents without having access to it. I think to solve it on a technical level we need to solve the RBAC story, The how, the who and why would want to have access to that information.

[ruflin]

@ph Agree. I would assume we have the same question around all monitoring data from the agent and its processes? (logs and metrics). Or would you consider this here different?

[ph]

I believe they should have the same rules applied to them.

[mostlyjason]

Yeah people can always apply index permissions if they want to restrict it. Should be easier with our new indexing strategy.

[mostlyjason]

Making a note here that on an email thread we decided to hide non-local metadata since it's a potential Gold+ feature