# How useful Kibana is for reporting purpose

**URL:** <https://discuss.elastic.co/t/how-useful-kibana-is-for-reporting-purpose/208866>\
**Category:** Kibana\
**Created:** [November 21, 2019, 11:19am UTC](https://discuss.elastic.co/t/how-useful-kibana-is-for-reporting-purpose/208866 "2019-11-21T11:19:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ksarkar](https://avatars.discourse-cdn.com/v4/letter/k/ee7513/32.png) [@ksarkar](https://discuss.elastic.co/u/ksarkar)\
**Post date:** [November 21, 2019, 11:19am UTC](https://discuss.elastic.co/t/how-useful-kibana-is-for-reporting-purpose/208866/1 "2019-11-21T11:19:31Z")

</div>

We understand that Kibana is very much helpful in case of Data Aggregation and analytics specially with strong set of graph tools. My concern is how useful kibana is for reporting purpose, like detail usage, stock reports etc ?  
joining several indices and use search on that ?

is that ok or not recommended. If I wish to do those with millions of data spreader over indices what are things that I should remember as best practices ?

---

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [November 21, 2019, 12:26pm UTC](https://discuss.elastic.co/t/how-useful-kibana-is-for-reporting-purpose/208866/2 "2019-11-21T12:26:18Z")

</div>

Well as long as you can ingest your data Kibana can 'report' on them. But it's not good at joining indicies like between relation tables in a rDBMS, so your data should not be 'normalized' into different indices: I would say one BCP is a bit like with other noSQLs ingest your data so they can answer your questions.

---

<div class="post-metadata">

**Author:** ![ksarkar](https://avatars.discourse-cdn.com/v4/letter/k/ee7513/32.png) [@ksarkar](https://discuss.elastic.co/u/ksarkar)\
**Post date:** [November 21, 2019, 1:53pm UTC](https://discuss.elastic.co/t/how-useful-kibana-is-for-reporting-purpose/208866/3 "2019-11-21T13:53:38Z")

</div>

So, it can be assumed it could be done only if we can model data ingest before sending it to indices rather going to perform any join query on those data ? rDBMS type though process may not helpful either.

---

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [November 21, 2019, 2:49pm UTC](https://discuss.elastic.co/t/how-useful-kibana-is-for-reporting-purpose/208866/4 "2019-11-21T14:49:18Z")

</div>

Yes if you can create a time serie of 'event documents' containing the field data you later wish to 'query' graph the trend of then yes no problem.

Not sure if elastic new KQL could perform some form of join or if the SQL-ish interpreter in Canvas only applies to Canvas.

Any Elastic member to elaborate on this here?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 19, 2019, 2:49pm UTC](https://discuss.elastic.co/t/how-useful-kibana-is-for-reporting-purpose/208866/5 "2019-12-19T14:49:19Z")

</div>

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