-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mimir-distributed] Frequently Gaps Inside Mimir Metrics #1517
Comments
Active Alerts:
|
Config:
|
mimir-distributed-distributor log:
|
mimir-distributed-ingester log:
|
prometheus-rancher-monitoring-prometheus log:
|
Config:
|
Hi, out-of-order sample support is an upcoming feature in Mimir (grafana/mimir#2187). Possibly @codesome can comment on this issue? |
Mimir 2.2 will have experimental support for accepting out of order samples. The release will come with docs on how to enable this feature and use this. Stay tuned! |
Very nice. But what about a alternative solution until then? How can i tell prometheus not to send old samples? How can i disable this behaviour? I know this is a question for another issue in another place but i am curious. :) |
Hello,
we got an running instance of mimir-distributed inside our kubernetes cluster. But there are still some problems. It seems to me that the samples, which are out of order, can not get ingested. I think prometheus tries to remote write old samples from its WAL. What do i need to configure in mimir to allow prometheus to send these old samples? How do i archive a gapless traffic of samples? If i take a look at mimir trough grafana i got some empty gaps (time ranges with no data) in the graph for every metric. What am i doing wrong here?
I added our config. Also logs of the mimir-distributed-distributor, mimir-distributed-ingester and prometheus-rancher-monitoring-prometheus pods.
Best Regards
The text was updated successfully, but these errors were encountered: