loguru sink
Updated 1 October 2026 · BugsRadar team
One sink for loguru: records at ERROR and above go to your channels with the exception, its traceback and the values bound with logger.bind. loguru is not a dependency of the package.
Install the package and call init first: see Install and Set it up. The API key is secret: where it may go.
Add the sink
loguru writes past the logging module, so init does not see it. Add the sink after your own loguru setup - logger.remove() without an id removes every sink, this one too:
import os
import bugsradar
from loguru import logger
bugsradar.init(api_key=os.environ["BUGSRADAR_KEY"])
logger.add(bugsradar.LoguruSink()) # ERROR and above; LoguruSink("WARNING") for more
What arrives
logger.exception brings the exception with its traceback, and values bound with logger.bind arrive as properties. loguru keeps only the formatted text, so BugsRadar groups messages with numbers, ids and quoted values masked. If you route logging into loguru with an InterceptHandler, those records are sent once, by init.
What the message looks like in the chat, how repeats are counted and when errors are bundled: see What you receive.
Next: Django →