First run

[David Vaccaro]

I have set up BugLog and I get the error
A timeout occurred while attempting to lock frAppStart_bugLogHQ.
Any ideas? I tried removing the lock and it just never finishes
loading

[Oscar Arevalo]

No, never seen that happening before. Did you check the config/buglog-config.xml.cfm to see that the DB settings are correct for your environment? Also what CFML engine/version and DB are you running?

--
Oscar Arevalo

http://about.me/oarevalo
http://www.coldbricks.com - Content Management System
http://www.oscararevalo.com - My Blog

[David Vaccaro]

There seamed to be some sort of glitch that deleted all tables... may
have been a fopar on my part.
Do you have a sample of how to get an application to report to bugLog?

On Feb 22, 1:06 pm, Oscar Arevalo <oarev...@gmail.com> wrote:
> No, never seen that happening before. Did you check the
> config/buglog-config.xml.cfm to see that the DB settings are correct for
> your environment? Also what CFML engine/version and DB are you running?
>

[Oscar Arevalo]

Sure, you can look here for a brief description of the process:

http://www.bugloghq.com/?page=docs#integrate

Also, you can take a look at /bugLog/test/client.cfm to see how it's used.

The gist of it is:

- create an instance of /bugLog/client/bugLogService.cfc configured with the address of your buglog server (buglog works best on a distributed environment, with buglog on a different server than your app, but you can have both buglog and your app on the same server if you want)

- put the instance you created on a persistent scope such as the Application scope

- whenever you trap an error in your app, call the notifyService() method in your buglogservice instance.

NotifyService() can take the following parameters:

- message:  The mesage of the error

- exception:  The cfcatch structure (but could be an empty struct if you dont have a cfcatch)

- extraInfo:  Anything you want, could be a string value, a struct, an array

- severityCode:  A classification for your error, you can use any value you want here, however buglog prefers the values INFO, ERROR, FATAL, CRITICAL, HTML and 404

Hope this helps!

Oscar