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

Question about query syntaxe #184

Closed
jsm-oxa opened this issue Jun 21, 2013 · 4 comments
Closed

Question about query syntaxe #184

jsm-oxa opened this issue Jun 21, 2013 · 4 comments

Comments

@jsm-oxa
Copy link

jsm-oxa commented Jun 21, 2013

Hi,

I wonder what is the best way to query.

Currently I write a query like this :
"@fields.ip:127.0.0.1 OR @fields.ip:123.456.789.0"

But I can get same results by using a query like this "127.0.0.1 OR 123.456.789.0".

Use "@fields" to query in a specific field is quicker isn't it ?

"127.0.0.1 OR 123.456.789.0" queries in @message ?

Thank you for the answer,

jsm-oxa

@rashidkpc
Copy link
Contributor

When you don't specify the field to search in, Elasticsearch looks in _all, unless you disable it in your mapping. In that case you'd either need to specify a new default field, or specify the field in every search.

Here is the query syntax documentation: https://lucene.apache.org/core/3_5_0/queryparsersyntax.html

@jsm-oxa
Copy link
Author

jsm-oxa commented Jun 21, 2013

Thank you very much for this quick answer, I posed the question because I found a way to hide the "@fields" display in field and table panel.
(a truncate filter in module.html)

@rashidkpc
Copy link
Contributor

I choose not to modify the field display to match the logstash schema because a) it would tie kibana to a single application and b) the logstash schema is getting rid of @fields soon

@jsm-oxa
Copy link
Author

jsm-oxa commented Jun 21, 2013

Ok thank you, I did it because we have a very little new project for a "special" client and we don't allow to query ES in his dashboard so hide @fields is prettier :)

Great news for logstash ! Youpi !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants