Query vs index

(charles barbosa) #1

This is probably an easy question so I apologize for this post,but there is just one thing I'm not understanding:

What does the querying do? It seems all of the mapping and filtering takes place in creating the index.
After that you utilize cabana to structure out the dashboard.

Is there something you can do specifically with the queries or are the queries used to structure an index?

(Mark Walkom) #2

When you build dashboards with Kibana, it populates those using queries.

So queries ask questions of the indexed data and then return the results of those questions.

(charles barbosa) #3

So I index my data using curl, or dev tools.
I can then run queries against the data in Dev tools, but I don't see what it does? It returns a result..but what do I do with the result?
You build the dashboard in kibana based off of the index settings

im just not seeing how queries manipulates anything.

sorry for the easy question .

(Mark Walkom) #4

Yes, or Logstash or Filebeat or even something else you have that can send data to Elasticsearch.

The index settings simply tell Kibana which index it needs to be looking at.

Think of it this way - You put data in a database table, you then query that to get results, you then take those results and put them into a report or a dashboard or to pass to another application.
Elasticsearch is no different, the logical process is the same.

(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.