Nick Dichev

@mruoss Great, thanks for the quick response. I did notice that you added metadata to these logger calls so that was going to be my "nuke it" plan! Do you...

Hi @samharnack @DeemoONeill I've implemented the idea being discussed in #51 if you want to take a look

@s3rius thanks for the fix, I was debugging the middleware a bit today and I noticed that the `startup` callback wasn't being executed. I read the prometheus client documentation's section...

@s3rius yes I still get the error on 0.8.3 -- the only way I've been able to resolve the `Duplicated timeseries in CollectorRegistry: {'found_errors_total', 'found_errors', 'found_errors_created'}` error is with my...

@s3rius Yes that makes since. In fact, your comment made me realize my application does have some metrics in another registry which don't make sense to collect/expose from the primary...

@s3rius Interesting, I was able to do some more debugging with your example. I was able to run your example just fine. What I noticed however, is that it did...

No I only have one broker. ```python3 # src.nebula.broker from uuid import uuid4 import os from taskiq import InMemoryBroker, TaskiqEvents, TaskiqState, PrometheusMiddleware from taskiq_redis import ListQueueBroker, RedisAsyncResultBackend from nebula.config import...