Hi Team,
please explain why we need to use saved searches in kibana?
what is the difference if we use the saved search vs search pattern in visualization.
Please let me know how is it going to impact the performance
Thanks in advance
Hi Team,
please explain why we need to use saved searches in kibana?
what is the difference if we use the saved search vs search pattern in visualization.
Please let me know how is it going to impact the performance
Thanks in advance
Are you referring to the performance difference between using a saved search as the basis for a visualization, as opposed to typing the same search filter into the filter/query bar? There is no performance difference, it's just a convenient feature.
Thanks for reply,
yes, I am referring the same.
where are we going to get the advantage of saved search, please let us know.
Just to be clear, we're talking about the following option which is high-lighted below?
Using this doesn't give you a performance improvement, it's only a convenient feature when you want to reuse a saved search that you've already created in the Discover application.
Yes, correct
I am trying to understand when we open a visualization how is the saved search impacting the performance of dashboard.
when we are creating visualizations we can do 2 ways,
one way is to create a search and save it. In the visualization creation screen, we can select as you have mentioned above.
the other way is you can do a search there it self in visualization by selecting only Index on the above screen.
Both ways have the same performance.
Thanks for the clarification !!
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.