Currently when we deploy taskotron-trigger, we overwrite /etc/fedmsg.d/logging.py which is provided by infra with our own file. It redirects all fedmsg-hub messages to /var/log/fedmsg/taskotron-trigger.log. That has the unfortunate consequence that infra thinks the service is not working properly, because they don't see any messages from it (in the journal, or I don't know where).
/etc/fedmsg.d/logging.py
/var/log/fedmsg/taskotron-trigger.log
Find a way to keep important trigger messages logged, while not stealing all the usual fedmsg info from the expected locations. Maybe we don't need a custom file and using the journal would be enough for us?
Metadata Update from @kparal: - Issue priority set to: Normal - Issue tagged with: infra
Log in to comment on this ticket.