Component(s)
loki.write
Add a description
When wal is enabled for loki.write we have a single shared WAL for all configured endpoints, this is all fine. But we also have a marker that will keep track what segments have been sent. We create this marker per endpoint. The problem is that the marker file will be shared so latest write to this file will win. So when alloy restarts all endpoints will pick up from the segment that was latest written by any endpoint for a single loki.write component.
To fix this we need a per endpoint marker file instead of per component, we also need to be able to gracefully migrate from the old path to the new path for these files. Or we change the marker file format to something that supports multiple endpoints, e.g. JSON like the plan is for promethues savepoints.
Tip
React with 👍 if this issue is important to you.
Component(s)
loki.write
Add a description
When wal is enabled for loki.write we have a single shared WAL for all configured endpoints, this is all fine. But we also have a marker that will keep track what segments have been sent. We create this marker per endpoint. The problem is that the marker file will be shared so latest write to this file will win. So when alloy restarts all endpoints will pick up from the segment that was latest written by any endpoint for a single
loki.writecomponent.To fix this we need a per endpoint marker file instead of per component, we also need to be able to gracefully migrate from the old path to the new path for these files. Or we change the marker file format to something that supports multiple endpoints, e.g. JSON like the plan is for promethues savepoints.
Tip
React with 👍 if this issue is important to you.