# Using ElasticSearch for logs

**URL:** <https://discuss.elastic.co/t/using-elasticsearch-for-logs/66062>\
**Category:** Elasticsearch\
**Created:** [November 15, 2016, 6:47am UTC](https://discuss.elastic.co/t/using-elasticsearch-for-logs/66062 "2016-11-15T06:47:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hhkx](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@hhkx](https://discuss.elastic.co/u/hhkx)\
**Post date:** [November 15, 2016, 6:47am UTC](https://discuss.elastic.co/t/using-elasticsearch-for-logs/66062/1 "2016-11-15T06:47:50Z")

</div>

Hi there,

I am new to ElasticSearch. So I need your kind helps.

We are developing a huge environment on smart meters and have been researching some searching tools to use it fast for logs.

We are planning to log every action of all users and some behaviours of all meters. Something like "UserX removed meterThis", "meterThat's signal is %75" etc.

So as you may imagine there will be around 10 million logs per day.

What we think to use ElasticSearch in this system is that when a system administrator wants to search a spesific user's activity or a meters behaviour...

So I am asking now firstly can ElasticSearch handle this amount of data?

And why should I use ElasticSearch not a bigdata database solution like MongoDB?

Hopefully, I haven't been the one who expects everything to be handed on a silver platter.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 15, 2016, 7:34am UTC](https://discuss.elastic.co/t/using-elasticsearch-for-logs/66062/2 "2016-11-15T07:34:13Z")

</div>

From an Elasticsearch perspective 10 million events a day is not necessarily very much. I have seen clusters handling [billions of events per day](https://www.elastic.co/blog/elasticon-video-of-the-week-verizon), so suspect data volume will not be a issue here. Elasticsearch offers flexible querying out of the box as well as a wide range of powerful aggregations. Whether these features and flexibility will make it easier to develop your solution or some other data store works just as well for your requirements you will need to decide.

---

<div class="post-metadata">

**Author:** ![hhkx](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@hhkx](https://discuss.elastic.co/u/hhkx)\
**Post date:** [November 15, 2016, 9:06am UTC](https://discuss.elastic.co/t/using-elasticsearch-for-logs/66062/3 "2016-11-15T09:06:51Z")

</div>

Well, thanks for your reply Christian.

---

<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 13, 2016, 9:06am UTC](https://discuss.elastic.co/t/using-elasticsearch-for-logs/66062/4 "2016-12-13T09:06:53Z")

</div>

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