Kibana version:
v9.2.4
Describe the bug:
My example : my control should list all the tenant names found in data.
For a 1 year range, it does not propose some recently created tenants.
The option to consider then is : "Ignore timeout for results"...
BUT i lost 1 hour to find it...
(All below is from Elastic IA Assistant)
What's actually happening
So the real bug is:
Over a large time range, the aggregation query takes longer
Kibana hits a timeout before the query completes
It returns partial results silently — no warning, no error, nothing
Tenants with fewer documents (like solar) simply don't make it into the partial result
Why the option name is terrible
"Ignore timeout for results" tells you what it does technically, but completely fails to tell you why you'd need it. A user-friendly name would be something like:
✅ "Wait for complete results (may be slower)"
✅ "Return all values, even if it takes longer"
✅ "Ensure complete list (disable early timeout)"
And most critically — when the timeout is hit and results are partial, Kibana should show a visible warning like:
⚠️ "Results may be incomplete due to timeout. Enable 'Ignore timeout' for full results."
Without that warning, users just assume the list is complete and lose data silently. That's a serious UX failure, not just a naming issue.
Steps to reproduce:
just have a large set of data with small subsets inside.
Kibana version:
v9.2.4
Describe the bug:
My example : my control should list all the tenant names found in data.
For a 1 year range, it does not propose some recently created tenants.
The option to consider then is : "Ignore timeout for results"...
BUT i lost 1 hour to find it...
(All below is from Elastic IA Assistant)
What's actually happening
So the real bug is:
Over a large time range, the aggregation query takes longer
Kibana hits a timeout before the query completes
It returns partial results silently — no warning, no error, nothing
Tenants with fewer documents (like solar) simply don't make it into the partial result
Why the option name is terrible
"Ignore timeout for results" tells you what it does technically, but completely fails to tell you why you'd need it. A user-friendly name would be something like:
✅ "Wait for complete results (may be slower)"
✅ "Return all values, even if it takes longer"
✅ "Ensure complete list (disable early timeout)"
And most critically — when the timeout is hit and results are partial, Kibana should show a visible warning like:
Without that warning, users just assume the list is complete and lose data silently. That's a serious UX failure, not just a naming issue.
Steps to reproduce:
just have a large set of data with small subsets inside.