What is it?
- It’s a service that runs every 15 seconds. It is responsible for doing all the work that is not done by a user in the web interface, for instance, if someone sends an email, this import it in the background.
- As of 8.8.55 and including it, it was known as FogBugz maintenance service, for later versions it is now called Heartbeat Pinger, uses the same concept but both do different tasks depending on the version.
Here’s a list of what the heartbeat does:
- Bayesian Training
- Backfills (Database normalization, like setting the ixBugEventLatest in the Bug table to the actual latest BugEvent for that case.)
- Check POP3 Mailboxes
- Daily tasks like sending the Escalation Report
- Send outgoing mail from the MailQueue table
- Search Indexing
- Schedule Maintenance
- Plugin heartbeat tasks (depends on the plugins you have installed)
- Minor Cleanup
Agent, End-User, Admin
Who will use it?
- It can be used by the End Users and Site admins by the configuration setting at Admin>Site Configuration>Advanced or using the service constructed URL shortcut /Heartbeat.asp
*Note: when you load this page in a browser it can conflict with its operation if you see the message “Heartbeat is locked. If you are sure there are no other processes running heartbeat, you can break the lock and reload heartbeat” you should load the page again until you don’t clash with the existing lock.*
How is it used?
- By accessing Site configuration or using the /heartbeat.asp URL shortcut
- If you’re debugging this service, use the following flags to skip a given part of a heartbeat. These flags can be set in the registry, as strings, REG_SZ (HKLM\SOFTWARE\Fog Creek Software\FogBugz\c:/yourfogbugz/website) or as a part of the request to the heartbeat.
List of all available flags:
*Note: Heartbeat will skip a given step if the flag is to true in either location(e.g. Will still skip daily tasks if fSkipDailyTastk is “1” in the registry and “o” in the request or vice versa*