We used to have the heartbeat publisher (http://hg.mozilla.org/automation/pulseshims/file/tip/heartbeat.py) running on a machine in the Pulse cluster, when it was in our data centre. Now that we've outsourced the main part of Pulse (the RabbitMQ cluster), we can no longer run this publisher there. It should be fairly easy to add this to PulseGuardian itself, as a worker daemon. We may want to consider celery tasks later, but since this is standalone, i.e., not controlled by any UI in PulseGuardian, this can be done later.
You need to log in before you can comment on or make changes to this bug.