Sean Glover

I'm not sure I understand the question, but as long as you use a user that has the permissions Kafka Lag Exporter needs, you can use that.

It may be worthwhile to reduce the `lookup-table-size` configuration if you experience these kinds of spikes regularly. That will give the lag-seconds calculation a "shorter memory" to draw upon, although...

On second thought, decreasing the `lookup-table-size` won't help. I'll have to do some experimentation with large increases like these to see if there's an elegant way to minimize their inaccuracy....

I've thought about this issue a little more. The problem is that in situations when regular consuming throughput is a fraction of the potential throughput a consumer can accommodate then...

@hisabimbola Not yet. I'll need some time to work on it, but I've been fairly busy. If you, or anyone else is interested in working on it I would welcome...

> We would like to know which progress you are facing related with this issue Unfortunately, I don't have much time to work on what I proposed earlier in this...

Sure. I'll look into this eventually. Feel free to open a PR in the meantime! Ideally we can make the library available on the classpath and override it with helm...

Thanks for reporting. This is a little tricky to troubleshoot because it's not clear from the stack trace what user code is associated with the exception. I wonder if it's...

I'm still unable to reproduce this. I tried running integration tests against Kafka 1.1, but they were successful. I suspect it's a combination of app configuration and Kafka API state....

Please provide configuration as well.