However, the scope of the linked issue is only about the raw functionality enabled by a query parameter.
To make this feature useful for users currently using Discover, two parts are necessary:
For the current data view, check whether there are failure store documents in the current time range. If that's the case, show a small indicator in the UI that signals "The data you are viewing might not be complete, some documents were not indexed correctly".
There is a way to "flip on" the query parameter to show the failure documents. There are multiple ways how this could look like:
Just add the query parameter - currently selected columns might not fit well
Open a separate view in a new tab with the relevant columns preselected
To determine whether there are failed docs, we can take the current index pattern (either via data view or via from clause of the ESQL query) and query it for the current time range, just retrieving a single document ("size": 1 / | limit 1) - if this returns something, we have failed documents. This request can happen in the background, not blocking the other user-visible data requests
https://github.com/elastic/kibana/issues/184092 paves the way to explore failure store documents in Discover.
However, the scope of the linked issue is only about the raw functionality enabled by a query parameter.
To make this feature useful for users currently using Discover, two parts are necessary:
Implementation notes
from
clause of the ESQL query) and query it for the current time range, just retrieving a single document ("size": 1
/| limit 1
) - if this returns something, we have failed documents. This request can happen in the background, not blocking the other user-visible data requests