Need a different way of handling UMB resubscription for image/trigger jobs

Currently, we have a timer kicking off our image jobs and trigger jobs for UMB resubscription with "{}" as the message.     The timer executes frequently to make sure the jobs are resubscribed frequently and available for when they are triggered.

The issue with this is that we're polluting the logs of all of the image jobs and triggers.    For example 

https://ci-jenkins-csb-fuse.apps.ocp4.prod.psi.redhat.com/job/Productization/job/fuse-osbs-build-trigger-console/

we're not keeping a ton of logs because we have space issues, and it's getting hard to debug whether a job kicked off, and if I kick off a job on a Friday, the log for it will be gone by Monday.

We need some solution to resubscribe these jobs frequently that doesn't generate a log for that job.