From c303c9e9d02ebdc813ed0e53533c29b1139b2e8f Mon Sep 17 00:00:00 2001 From: Rashid Khan Date: Wed, 1 Oct 2014 15:45:46 -0700 Subject: [PATCH] Update K3_FAQ.md Fix line breaks --- K3_FAQ.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/K3_FAQ.md b/K3_FAQ.md index 44187265ce6b..9436c70d6081 100644 --- a/K3_FAQ.md +++ b/K3_FAQ.md @@ -1,13 +1,13 @@ **Kibana 3 Migration FAQ:** -**Q:** Where is feature X that I loved from Kibana 3? +**Q:** Where is feature X that I loved from Kibana 3? **A:** It might be coming! We’ve published our immediate roadmap as tickets Check out the beta labels to see if the feature you’re missing is coming soon. -**Q:** Is the dashboard schema compatible? +**Q:** Is the dashboard schema compatible? **A:** Unfortunately they are not compatible, in order to achieve the features we wanted it simply was not possible to keep the same schema. Aggregations work fundamentally different from facets, the new dashboard isn’t tied to rows and columns and the relationships between searches, visualizations and the dashboard are complex enough that we simply had to design something more flexible. -**Q:** How do I do multi-query? +**Q:** How do I do multi-query? **A:** The ‘filters’ aggregations will allow you to input multiple queries and compare them visually. You can even use Elasticsearch JSON in there! -**Q:** What happened to templated/scripted dashboards? +**Q:** What happened to templated/scripted dashboards? **A:** Check out the URL, the state of each app is stored there, including any filters, queries or columns. This should be a lot easier than constructing scripted dashboards. The encoding of the URL is RISON.