# Icinga2 Graphite

**URL:** <https://community.icinga.com/t/icinga2-graphite/4028>\
**Category:** Icinga Web\
**Tags:** graphite\
**Created:** [April 7, 2020, 8:31pm UTC](https://community.icinga.com/t/icinga2-graphite/4028 "2020-04-07T20:31:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bsheqa](https://community.icinga.com/user_avatar/community.icinga.com/bsheqa/32/9_2.png) [@bsheqa](https://community.icinga.com/u/bsheqa)\
**Post date:** [April 8, 2020, 7:33am UTC](https://community.icinga.com/t/icinga2-graphite/4028/2 "2020-04-08T07:33:45Z")

</div>

Graphites storage schema in combination with Icinga is tricky sometimes. Configuring a storage schema in graphite that does not match the check interval can lead to a state where Graphite can not properly aggregate the metrics. Hence, you will have (large) gaps in your graphs.

In our docs we have a recommended storage schema for Graphite: [https://icinga.com/docs/icinga2/latest/doc/14-features/#graphite-carbon-cache-writer](https://icinga.com/docs/icinga2/latest/doc/14-features/#graphite-carbon-cache-writer)

Still, if you have different check intervals, you have to make sure that you have a storage schema configured with a matching pattern and retention.

---

_[View the full topic](https://community.icinga.com/t/icinga2-graphite/4028)._