Skip to content
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

Easier query building interface for admin analytics #15

Closed
GUI opened this issue Dec 3, 2013 · 1 comment
Closed

Easier query building interface for admin analytics #15

GUI opened this issue Dec 3, 2013 · 1 comment

Comments

@GUI
Copy link
Member

GUI commented Dec 3, 2013

Currently in in the analytics admin, nearly all filtering and querying of analytics is performed via the advanced filters using Lucuene's query syntax. This gives a lot of flexibility in doing complex nested AND, OR, wildcard, range, etc type queries, but the syntax is less than obvious to people getting started. It would also help accommodate simpler queries in a more intuitive way (for example, not having to remember to escape backslashes in URL paths like request_path:\/nrel\/*).

I think this could be a fairly simple query building interface to start with: select a known field, select a matcher (begins with, ends with, contains, etc) and then enter your search value. Click a plus to add another query row, and all your inputs get ANDed together. As long as we keep around the advanced filters input for handling more advanced logic, I think this would be a simple way to making the analytics querying much easier to use 95% of the time.

It might also be worth looking into Kibana again (demo. When I first set about building this interface Kibana was only built for Logstash, but it's become a lot more generic and is now a client-side only JS app that could easily be dropped anywhere elasticsearch is running. I'm still not entirely sure this meets our needs since it's interface seems pretty advanced and I'm not sure it fits some of our other needs (like hiding certain sensitive fields or only making segments of the data available to certain users), but it's probably worth another look.

@GUI GUI added this to the v0.7 milestone Jan 19, 2015
@GUI GUI removed this from the v0.7 milestone Feb 10, 2015
@GUI GUI added this to the v0.8 milestone Feb 20, 2015
@GUI
Copy link
Member Author

GUI commented Feb 20, 2015

Implemented in master on NREL/api-umbrella-web#7 This will be part of the v0.8 release.

The pull request as more details, but it basically looks like:

screen shot 2015-02-19 at 5 31 19 pm

@GUI GUI closed this as completed Feb 20, 2015
GUI added a commit that referenced this issue Sep 27, 2015
GUI added a commit that referenced this issue Sep 27, 2015
Add ability to have wildcard backend hostnames
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant