Debugger Interceptors

CBDebugger emits several interception events

The debugger can be extended by listening to several events it fires. Here is a collection of such events and the data they emit.

Event	Description
beforeDebuggerPanel	Before the debugger panel is rendered
afterDebuggerPanel	After the last debugger panel is rendered
beforeProfilerReportPanels	Before any individual profiler report panels are rendered
afterProfilerReportPanels	After any individual profiler report panels are rendered
onDebuggerLoad	Fires after the module has fully loaded and been configured with all runtime settings
onDebuggerUnload	Fires after the module is unloaded
onDebuggerRequestTrackerCreation	When the request tracker has been created and placed in request scope
onDebuggerProfilerRecording	Before the request tracker is saved in the profiler, last chance to influence the recording

beforeDebuggerPanel / afterDebuggerPanel

Location of UI Events

Data	Description
debuggerConfig	The debugger configuration struct
debuggerService	The debugger service object

beforeProfilerReportPanels / afterProfilerReportPanels

Location of UI Events

Data	Description
debuggerConfig	The debugger configuration struct
debuggerService	The debugger service object
profiler	The full profiler report structure

onDebuggerLoad / onDebuggerUnload

No event data emitted

onDebuggerRequestTrackerCreation

This event is fired once the debugger is ready to start tracking the request. You can use the structure to incorporate anything into it.

Data	Description
requestTracker	The request tracker structure you can use to add your own data collection for the request.

onDebuggerProfilerRecording

This event is fired right before the request tracker struct is stored in permanent storage. Your last chance to add data into the tracker structure.

Data	Description
requestTracker	The request tracker structure you can use to add your own data collection for the request.