# Graphite resets graphs after each server reboot

**URL:** <https://community.icinga.com/t/graphite-resets-graphs-after-each-server-reboot/7646>\
**Category:** Visualization, Metrics & Reporting\
**Tags:** graphite-web\
**Created:** [June 22, 2021, 5:23pm UTC](https://community.icinga.com/t/graphite-resets-graphs-after-each-server-reboot/7646 "2021-06-22T17:23:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![homerjay](https://community.icinga.com/user_avatar/community.icinga.com/homerjay/32/377_2.png) [@homerjay](https://community.icinga.com/u/homerjay)\
**Post date:** [June 23, 2021, 8:52am UTC](https://community.icinga.com/t/graphite-resets-graphs-after-each-server-reboot/7646/2 "2021-06-23T08:52:04Z")

</div>

Hi.

As a starting point, it would be interesting to know if the whisper files are really no longer present.

Maybe you could look for the whisper files (e.g. at /opt/graphite/storage/whisper/icinga2/…) and check if older performance-data is present.  
Look for the tool **whisper-fetch.py** , which accepts an “Unix Epoch Timestamp” for the argument

```auto
"--from"

```

Syntax:

```auto
/path/to/whisper-fetch.py <path-to-whisper-file> --from=<timestamp_from_when> [--pretty]

```

Example:

```auto
/opt/graphite/bin/whisper-fetch.py max.wsp --from=1624177772 --pretty
# or : /opt/graphite/bin/whisper-fetch.py max.wsp --from=1624177772 --pretty | head

```

If there is no data present older than 1 day, you should have a look at the  
storage-schemas.conf. [This](https://community.icinga.com/t/fehler-bei-graphite-in-der-historie/6886/5) excellent post might be helpful.

Hope it helps.

* * *

Greetings.

---

_[View the full topic](https://community.icinga.com/t/graphite-resets-graphs-after-each-server-reboot/7646)._