# ElasticSearch as metrics database

**URL:** <https://discuss.elastic.co/t/elasticsearch-as-metrics-database/28820>\
**Category:** Elasticsearch\
**Created:** [September 8, 2015, 7:59am UTC](https://discuss.elastic.co/t/elasticsearch-as-metrics-database/28820 "2015-09-08T07:59:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![matejzero](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@matejzero](https://discuss.elastic.co/u/matejzero)\
**Post date:** [September 8, 2015, 7:59am UTC](https://discuss.elastic.co/t/elasticsearch-as-metrics-database/28820/1 "2015-09-08T07:59:27Z")

</div>

Hello,

with the coming ElasticSearch support in Grafana and ES 2.0, ES starts to look interesting as a metrics backend.

Is anyone using it already?  
What kind of performance do you see? I plan on having around 500.000 - 1.000.000 metrics/s and another 2000 logs/s. Is that something that ES can take or is it too much? My cluster is quite small, 3 servers with 2x6cores(HT), 64gb of memory(can add more) and SAS hard drives.  
How do you send data to ES? Over Logstash or directly?  
Is some kind of metrics down sampling planned for ES?

Matej

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 8, 2015, 8:01am UTC](https://discuss.elastic.co/t/elasticsearch-as-metrics-database/28820/2 "2015-09-08T08:01:26Z")

</div>

Check out [ELK vs grafana+influxDB](https://discuss.elastic.co/t/elk-vs-grafana-influxdb/1686)

---

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [September 9, 2015, 4:28am UTC](https://discuss.elastic.co/t/elasticsearch-as-metrics-database/28820/3 "2015-09-09T04:28:17Z")

</div>

Hi Matej,

Is that 500K-1M metrics per second?  
If so, your cluster is definitely too small.

2K logs/s is not a problem. At least not ingestion. Queries are the bigger question. As is retention. For data volume you're referencing you'll need to seriously think about architecture/design, whether you use ES or InfluxDB (does it support sharding and replication now?)

## Otis

Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management  
Elasticsearch Consulting & Support \* [http://sematext.com/](http://sematext.com/)

---

<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:** [July 5, 2017, 11:51pm UTC](https://discuss.elastic.co/t/elasticsearch-as-metrics-database/28820/4 "2017-07-05T23:51:35Z")

</div>