[Fleet] logs dataset / level selection in Agent Logs view is not auto-refreshing the view with each click

[EricDavisX]

Kibana version:
8.0 - self-managed stack tested. latest 8.0 snapshot used. current hash in the server is:
07af5d3

Browser OS version:
chrome

Describe the bug:
When the user clicks in the Agent logs tab drop down selecteds, the UI was previously refreshing with each click to show the user the different logs. It isn't refreshing at all now, and with no 'apply' button the only way to change the log level is to 'jiggle' the date selector.

Steps to reproduce:

1. install agent
2. go to Fleet in Kibana and click on agent and select 'logs' tab
3. click the dropdown for 'dataset' and select a few. note the selection does not change.
4. due to likely Agent side bug, you need to refresh the date selector to get *any data to show up, which makes the problem quite clear

Expected behavior:
logs view refreshes with each click

Screenshots (if relevant):

Errors in browser console (if relevant):

Fleet-Logs-UI-selection2.mov

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[jen-huang]

@afgomez More LogStream component fun :) I wonder if this was impacted by #102980?

[EricDavisX]

For testers, fyi: a quick work-around is to refresh the UI page in the browser and it will pick up the change and show logs (no need to do the date picker which is not as easy to me, as the whole page refresh)

[afgomez]

I wonder if this was impacted by #102980?

I doubt it, since changing the datasets should change the query. I'll take a look nonetheless

[dikshachauhan-qasource]

Hi @EricDavisX

While performing exploratory today on 7,14 snapshot cloud-qa build, we have observed similar issue on Observability> logs tab.

• Logs are not filtered out when any filter criteria is applied at search bar.

Screenshot:

Build Details:

BUILD 42091
COMMIT fe3ea8ed1fc80caa3acd805d24a1e9ea882aa30f

Please let us know if anything else is required.

Thanks
QAS

[afgomez]

I wonder if this was impacted by #102980?

It was indeed because of it. Changing a ref.current doesn't trigger whatever needs to be triggered internally in React, so I used a useState hook instead in #103876

[EricDavisX]

I loaded up the latest 7.14 snapshot, fyi and it seems worse than before - I don't yet know if it is more Agent side interactions or just the Fleet / Logs-UI side, but I can't see the other datastreams in the Logs UI or in Fleet. They are there in Discover tho. : /

here is a movie showing a slightly differnt behavior. just in case helpful.

logs-ui-movie.mov

[jen-huang]

@EricDavisX The filter options missing is a different issue. This happens when there are no agent logs at all.