Can you integrate research with sub queries ?
(Like Splunk with the pipe)
Describe the feature:
In the toolbar, It would be interesting to be able to search with the results of an another query.
Could you provide some examples of how you would use this? The Kibana filter bar does support the full Elasticsearch query DSL, so you can craft any queries ES supports .
@Bargs Splunk query language more than just query language. It is Search Processing Langauge. This SPL provides a possibility to describe pipeline of data: Filtering, Aggregation, Transformation.
Following things definitely is missing in Lucene language:
All of these things you definitely can get if you will use multiple Kibana UI controls, but Splunk provides better UX if you know (!) query language.
Here is scenario example:
I would like to search over all HTTP logs to visualize the amount of 200 vs 500 responses.
In Splunk
index=haproxy (status=500 OR status=200) | timechart count by status
In this query | timechart count by status
is equal to two (!) aggregation that we apply to results that we get from query index=haproxy (status=500 OR status=200)
In Kibana (version 6.2.1)
status:200 OR status:500
As you can see it very inconvenient to performed ad-hoc analytics with Kibana. Even creating dashboards in Splunk is much easier than in Kibana.
Thanks for the details @torinaki. We've actually started working on a new query language which will enable us to build features like you've described. Here's a brainstorming ticket where we've been keeping a wishlist of features we'd like to add. I've linked to your comment so we don't lose the context but feel free to comment directly on that ticket if there's anything else you'd like to add. I'm going to close this issue since it has been superceded by more up to date tickets about the new query language.
Most helpful comment
@Bargs Splunk query language more than just query language. It is Search Processing Langauge. This SPL provides a possibility to describe pipeline of data: Filtering, Aggregation, Transformation.
Following things definitely is missing in Lucene language:
All of these things you definitely can get if you will use multiple Kibana UI controls, but Splunk provides better UX if you know (!) query language.
Here is scenario example:
I would like to search over all HTTP logs to visualize the amount of 200 vs 500 responses.
In Splunk
In this query
| timechart count by status
is equal to two (!) aggregation that we apply to results that we get from queryindex=haproxy (status=500 OR status=200)
In Kibana (version 6.2.1)
As you can see it very inconvenient to performed ad-hoc analytics with Kibana. Even creating dashboards in Splunk is much easier than in Kibana.