# Migrate Icinga2 metrics to ELK

**URL:** <https://community.icinga.com/t/migrate-icinga2-metrics-to-elk/3150>\
**Category:** Icinga Web Modules\
**Tags:** icingabeat, elk\
**Created:** [January 7, 2020, 2:37pm UTC](https://community.icinga.com/t/migrate-icinga2-metrics-to-elk/3150 "2020-01-07T14:37:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MoeJoe](https://community.icinga.com/user_avatar/community.icinga.com/moejoe/32/195_2.png) [@MoeJoe](https://community.icinga.com/u/MoeJoe)\
**Post date:** [January 7, 2020, 2:37pm UTC](https://community.icinga.com/t/migrate-icinga2-metrics-to-elk/3150/1 "2020-01-07T14:37:39Z")

</div>

Hy,

ive got a running icinga master with connect to my ELK.  
i ship the new metrics all to the ELK with the icingabeat and read them with the elastic module.  
so far so good…

but is there a way to migrate and properly index the old metrics which where actually only insight the local icinga postgresql DB to the ELK ?

---

<div class="post-metadata">

**Author:** ![dnsmichi](https://community.icinga.com/user_avatar/community.icinga.com/dnsmichi/32/7721_2.png) [@dnsmichi](https://community.icinga.com/u/dnsmichi)\
**Post date:** [January 7, 2020, 3:20pm UTC](https://community.icinga.com/t/migrate-icinga2-metrics-to-elk/3150/2 "2020-01-07T15:20:43Z")

</div>

Hi,

Icinga doesn’t store any metrics in the IDO database backend. It stores state changes, notifications, etc in historical tables if that’s of interest. Exporting such would require SQL magic and forwarding them to Elasticsearch then.

Question aside - why would you want to store metrics in Elastic Stack? Imho Graphite/InfluxDB/Prometheus solve a better TSDB purpose here.

Cheers,  
Michael

---

<div class="post-metadata">

**Author:** ![MoeJoe](https://community.icinga.com/user_avatar/community.icinga.com/moejoe/32/195_2.png) [@MoeJoe](https://community.icinga.com/u/MoeJoe)\
**Post date:** [January 9, 2020, 10:37am UTC](https://community.icinga.com/t/migrate-icinga2-metrics-to-elk/3150/3 "2020-01-09T10:37:16Z")

</div>

metrics should be stored in the ELK, cause the ELK is our global SIEM System.  
therefore we want all informations stored in there…

if its not posible (to easyly migrate the old metrics this isnt a deal breaker).

---

<div class="post-metadata">

**Author:** ![dnsmichi](https://community.icinga.com/user_avatar/community.icinga.com/dnsmichi/32/7721_2.png) [@dnsmichi](https://community.icinga.com/u/dnsmichi)\
**Post date:** [January 9, 2020, 11:13am UTC](https://community.icinga.com/t/migrate-icinga2-metrics-to-elk/3150/4 "2020-01-09T11:13:19Z")

</div>

Marketing did a good job here, I just read [https://www.elastic.co/products/siem](https://www.elastic.co/products/siem)

I doubt that metrics are a good idea in Elasticsearch in the long term, regarding aggregation, storage and performance, but truly it is your system and you’re taking the decisions and results.

In terms of migration possibilities I don’t see any, unless you kept storing existing performance data metrics in TSDB systems like Graphite, InfluxDB, etc.

Cheers,  
Michael

---

<div class="post-metadata">

**Author:** ![MoeJoe](https://community.icinga.com/user_avatar/community.icinga.com/moejoe/32/195_2.png) [@MoeJoe](https://community.icinga.com/u/MoeJoe)\
**Post date:** [January 29, 2020, 12:00pm UTC](https://community.icinga.com/t/migrate-icinga2-metrics-to-elk/3150/5 "2020-01-29T12:00:09Z")

</div>

hy michael,

thanks for your reply…  
ive discuss this internal with my team and the guys think that the effort of the migration is to small…

so this topic can be closed.