You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The system, running Debian 10 on an Intel NUC, was operating normally. However, there was a network connection interruption at approximately 12:10 PM on December 27. Despite the machine remaining powered on, Grafana's graphs stopped updating.
The data does not align correctly with the time axis in Grafana. There is a 29-minute gap in the displayed data from 12:06 to 12:35, even though InfluxDB contains the data for this period. The issue was resolved only after rebooting the machine.
Primary Issue:
Grafana's graphs exhibit missing segments, despite the data being properly recorded in InfluxDB and the machine running during that time period.
Data is present in InfluxDB, and the machine remained powered on.
Used InfluxDB shell (SELECT * FROM measurement) and confirmed that the data exists for the missing period.
A data gap is visible in Grafana panels between 12:06 and 12:35, even though the data exists in InfluxDB.
The time axis appears to have skipped 29 minutes.
Normal graph rendering resumed after a system reboot.
The timestamp in the Grafana query is correct.
Queries are correct, and we also tried to reproduce this issue on a machine with the same configuration, software, and hardware, but there were no time axis gaps in Grafana graphs, even without an internet connection.
For example purposes, here is the query to verify uptime data:
SELECT max("value") FROM "netdata.system.uptime.uptime"
WHERE time >= now() - 6h
GROUP BY time(1m) fill(null)
Please check the attached screenshot for reference.
Environment Details:
OS: Debian 10 Buster with Backported Kernel 5.10.0-0.deb10.16-amd64
Grafana Version: 7.3.6
InfluxDB Version: 1.8.1
Netdata Version: v1.31.0-68-g2e88104dd
Setup:
Data Collection: Netdata
Time-Series Database: InfluxDB 1.8.1
Troubleshooting Steps Taken:
Verified InfluxDB Data:
Checked Network & System Uptime:
Confirmed that the system was running during the affected period.
Restarted Machine:
Around 12:40 PM, the issue was resolved after unplugging and reinserting the power cable, followed by a system reboot.which restored normal functionality.
root@DEB-NUC11PAHS:~# last reboot
reboot system boot 5.10.0-0.deb10.1 Tue Jan 21 10:17 still running
reboot system boot 5.10.0-0.deb10.1 Fri Dec 27 12:36 still running
root@DEB-NUC11PAH:~# uptime
20:59:27 up 43 days, 10:42, 5 users, load average: 2.16, 2.03, 2.21
Additional Information:
While the network was down, InfluxDB continued collecting data, yet Grafana displayed missing data.
After rebooting the machine, Grafana started displaying data normally again.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Issue Description:
The system, running Debian 10 on an Intel NUC, was operating normally. However, there was a network connection interruption at approximately 12:10 PM on December 27. Despite the machine remaining powered on, Grafana's graphs stopped updating.
The data does not align correctly with the time axis in Grafana. There is a 29-minute gap in the displayed data from 12:06 to 12:35, even though InfluxDB contains the data for this period. The issue was resolved only after rebooting the machine.
Primary Issue:
Grafana's graphs exhibit missing segments, despite the data being properly recorded in InfluxDB and the machine running during that time period.
Data is present in InfluxDB, and the machine remained powered on.
Used InfluxDB shell (
SELECT * FROM measurement) and confirmed that the data exists for the missing period.Observations:
Queries are correct, and we also tried to reproduce this issue on a machine with the same configuration, software, and hardware, but there were no time axis gaps in Grafana graphs, even without an internet connection.
For example purposes, here is the query to verify uptime data:
Please check the attached screenshot for reference.
Environment Details:
Setup:
Troubleshooting Steps Taken:
Additional Information:
Beta Was this translation helpful? Give feedback.
All reactions