Discrepancy in Histogram Counts on OpenObserve
TLDR rito reported incorrect counts on the OpenObserve histogram. Hengfei explained this might be due to batch ingestion or lack of '_timestamp'; the former makes the server ingest logs rapidly while the latter causes high volume in a small time range. rito acknowledged the advice.
Jun 30, 2023 (5 months ago)
rito
06:18 AMHowever, the counts on the histogram may not be correct. It does not match the log count. This is not a critical issue for me, but I will report it.
Hengfei
06:19 AMrito
06:21 AMHengfei
06:25 AMHengfei
06:27 AM_timestamp
yourself, we will use the ingest time as _timetamp
, it will looks like your screenshot, in a small time range, it has high volume, but after minutes it reduced.rito
06:29 AMThanks for the info I will try sending it with
_timestamp
.OpenObserve
Indexed 406 threads (74% resolved)
Similar Threads
High Memory Usage Issue in OpenObserve 0.5.1
Chris reported high memory usage with OpenObserve 0.5.1 when making specific queries, causing out of memory errors. Hengfei suggested attempting without conditions. Chris will raise an official issue regarding the problem.
Query and Issue with Disparity in Stream Stats and Disk Usage
Karan shared a query and noted a disparity in stream stats and disk usage. After troubleshooting, Hengfei identified a bug and advised on stats refresh. Ashish confirmed that the disk size was the accurate measure and they would investigate the stats calculation.
OpenObserve issues with FluentBit and Dashboard
Alejandro experienced issues with FluentBit losing connection with OpenObserve and discarding logs, and an error when saving a chart on the OpenObserve dashboard. Prabhat could not identify the cause of record loss. However, potential solutions were suggested to save the dashboard with a string-type filter instead of integer one.