Lost historical data

  • What Grafana version and what operating system are you using?
    Grafana V9.0.1 and CentOS 7

  • What are you trying to achieve?
    Trying to get historical data more than 14 days.

  • How are you trying to achieve it?
    suddenly lost the data more than 14 days.

  • What happened?
    Previously we were able to see all historical data but not more than 14 days.

  • What did you expect to happen?
    Expect to see historical data through dashboards more than 14 days.

  • Can you copy/paste the configuration(s) that you are having problems with?
    No

  • Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.
    No

  • Did you follow any online instructions? If so, what is the URL?
    No.

Regards,
Kaps

  1. What is your data source?

  2. Does your data source contain data older than 14 days (check this
    independently of Grafana)?

Antony.

1 Like

hello,
it’s look likes it’s related to influxdb database, not really grafana, what is your version of influx ?
did you upgrade, change config or something like that recently ?

I already have dataloss one time with influxdb, it was miss configuration in the virtual machine. it corrupted his volume himself by writting on it (something to see with dynamical, disk memory allocation and other weird limitation)
actually not the database solution fault.

  1. What is your data source?
    pulling data from prometheus and DB as influxdb
  2. Does your data source contain data older than 14 days (check this
    independently of Grafana)?
    how to confirm it?

go on the influxdb interface and try your query,
check the data retention policy on your bucket too
you can query directly influxdb from grafana . did you try it ?
what is influxdb version ?

InfluxDB v1:

#order-by-time-desc

InfluxDB v2:

InfluxDB v2 using v1 query language:

Antony.

what is influxdb version ?

influxd version
InfluxDB v1.8.10 (git: 1.8 688e697c51fd)

Hi Team,

Updated /etc/systemd/system/prometheus.service as well but still no luck.

cat /etc/systemd/system/prometheus.service | grep retention
–storage.tsdb.retention.time=1y

Or else it will start keep retention data from now onwords after doing above steps?

Regards,
Kaps