Prometheus报错:Out of order sample from remote write #12064
Replies: 9 comments
-
Thank you for your report. I don't speak Chinese, but I asked Google Translate to convert "刚刚部署好Prometheus并无错误日志输出,运行一段时间之后突然容器日志里大批量的会刷这些日志,并且Prometheus里查询不到数据无法正常使用".
That seems to be a problem with something sending bad data to your Prometheus.
There is over an hour gap between these two log lines. Maybe the translation is bad - can you put more detail on when you got a large number of logs?
Do you get an error message? If so, please quote it exactly. If not, please explain what you do see. |
Beta Was this translation helpful? Give feedback.
-
Hi All, I had same issue as describe above. after I checked log error and found logs as following information : Log prometheus
Log in prometheus remote writer
I just read this information and I have check there is no duplicate targets, I have separate tagging for every prometheus. and just want to make sure is it error still related to this history ? thanks in advance |
Beta Was this translation helpful? Give feedback.
-
These errors are mostly caused by timestamp inconsistencies in the data or issues with the data source itself. It is important to note that time synchronization is critical. I would suggest making sure that the time of your servers are synchronized correctly. Additionally, make sure that you have set all external labels to be unique and consistent. If Prometheus is the sender, then ensure that all external labels used are unique across all instances. If the sender is not Prometheus, then check the sender's configuration and ensure that it is sending correctly formatted data with timestamps in order. |
Beta Was this translation helpful? Give feedback.
-
这个现象在清理过数据之后重启会恢复,但是运行一段时间就又会进行大量输出,并且导致Prometheus内查询不到监控项无法正常使用。 |
Beta Was this translation helpful? Give feedback.
-
顺便问一下开启out_of_order_time_window能解决这个问题吗,这个应该在哪个文件进行开启Prometheus.yaml吗 |
Beta Was this translation helpful? Give feedback.
-
Enabling |
Beta Was this translation helpful? Give feedback.
-
因为目前情况看收集的数据时间戳会有乱序的情况,没找到具体原因,启动out_of_order_time_window应该在哪个配置文件中配置。 |
Beta Was this translation helpful? Give feedback.
-
To enable the out_of_order_time_window, you will have to add it under the
|
Beta Was this translation helpful? Give feedback.
-
你们觉得这种情况除了远程写入的agent端时间问题,还会有什么原因导致这种情况,一般重启之后运行一天左右Prometheus就无法正常进行使用 |
Beta Was this translation helpful? Give feedback.
-
What did you do?
What did you expect to see?
。
What did you see instead? Under which circumstances?
刚刚部署好Prometheus并无错误日志输出,运行一段时间之后突然容器日志里大批量的会刷这些日志,并且Prometheus里查询不到数据无法正常使用
System information
Linux 3.10.0-1160.15.2.el7.x86_64 x86_64
Prometheus version
Prometheus configuration file
Alertmanager version
Alertmanager configuration file
。
Logs
Beta Was this translation helpful? Give feedback.
All reactions