Alex Simenduev
Alex Simenduev
@tinder-tder yep, it does this on each time catalog applied, because the module removes this setting, and in my workaround I add it. I only care that when I upgrade...
The issue is on source redis not destination. Anyway, I already finished running redis shake and migrated all the data, so not an issue for me anymore, but maybe others...
You seem to be running different tests, as mine [passes](http://pastebin.com/tHvNcyDX) all the tests once I fixed the EXECABORT issue.
`EXECABORT` fired when one of the command in MULTI series is failed. so I just commented out the bad `set` (something like: `multi1.set("foo2", require_error(name));`)
We are also interested in this ability.
@whaike I think this is duplicate of #17, did you read https://github.com/jirwin/burrow_exporter/issues/17#issuecomment-492010910 ?
If still relevant, I've refactored the exporter to use prometheus custom collector implementation, which will solve the issue with stale metrics. > Since it's a refactor [my repo](https://github.com/shamil/burrow_exporter) was hard-forked...
Any news regarding this? We desperately need this DLQ feature. Logstash DLQ helps us a lot and this is the only feature that keeps us from migrating
Thanks @jszwedko I will wait ;)
@dependabot recreate