What is it?
Diagnostics are included with FogBugz to make remote debugging easier. They are not available to FogBugz On Demand customers, though we are working to make the necessary functionality available.
Who will use it?
This information must be known by any agent willing to debug FogBugz on-premises installs.
How is it Used?
Here's a breakdown of the various steps in diagnostics. They pretty much break down into these classes, sanity checks that just check to see if the configuration is correct, diagnostics* which provide information that might be useful, and tweaks** that might serve to bring a misbehaving configuration back in line.
-1 ./diagnostics.asp?sStep=showcrc: Source Code Check
0 ./diagnostics.asp?sStep=testcookies: Browser Cookies*
1 ./diagnostics.asp?sStep=testlogin: Login Cookies Check
2 ./diagnostics.asp?sStep=testfilewrite: File System Permissions Check
3 ./diagnostics.asp?sStep=testregistrywrite: Registry Permissions Check
4 ./diagnostics.asp?sStep=testregistryinfo: Registry Information*
5 ./diagnostics.asp?sStep=testlicenseinfo: Licenses, License Insert Check, License Reset*
6 ./diagnostics.asp?sStep=testbackfills: ixBugEventLatest Backfill Check
7 ./diagnostics.asp?sStep=testroguecases: Rogue Case Check, Rogue Case Deletion
8 ./diagnostics.asp?sStep=testmail: SMTP Check
9 ./diagnostics.asp?sStep=testmailboxes: Mailbox Check (POP and IMAP)
10 ./diagnostics.asp?sStep=testplugins: Plugin Check (list), Enter No Plugins Mode
11 ./diagnostics.asp?sStep=testmaintenance: Maintenance URL Test
12 ./diagnostics.asp?sStep=teststoredprocs: Triggers & Stored Procedures Check (only works if the FogBugz user has access to INFORMATION_SCHEMA db in MySQL)
13 ./diagnostics.asp?sStep=fileupload1: File Upload Start
14 ./diagnostics.asp?sStep=fileupload2: File Upload Confirm
15 ./diagnostics.asp?sStep=testdebug: Turn on Debugging**
Once debugging is turned on, SQL may be run directly against the database (up to and including DROP DATABASE) at