-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Structured inputs for editable filters #5249
Comments
+1 |
Big 👍. This is really the minimum viable level of features for #1583, which is a disappointing implementation. At this rate, Kibana 4 will reach Kibana 3 level of usefulness just in time for the whole thing to be rewritten again in KB5. 😞 |
👍 Is there a timeline for 4.4.0? |
Completely agree with @davidski. |
How complicated would implementing this be? Is it something someone could do without knowing the Kibana codebase inside and out? Could the devs let us know where to start on it? Basically, if someone created a successful pull request for this feature, could it get into Kibana before 4.3? I don't think I'd have time to do it myself, but if it's an essential feature for someone who has a lot more invested in Kibana than I do, they might have the resources to point at it if they could get some direction. |
Sorry @jerrac but 4.3 went into feature freeze Friday. |
@spalger waou, already a feature freeze ? |
The target release date is soon :) |
Waou, I'm impressed... |
Just updated my kibana nodes to 4.2.0 yesterday, but happy to upgrade again for editable filters! :) |
You can already achieve such filtering since Kibana 4.3 |
In #1583 we are introducing ability to edit filters. The first phase of this (#5109) calls for a JSON based editor that is very flexible and allows introduction of advanced (arbitrary) filters.
To make it easier to interact with editable filters for common use cases, we should consider introducing form-based editors for common filter types, such as date, string, and number.
Here are some screenshots of how this was presented to the user in Kibana 3
The text was updated successfully, but these errors were encountered: