Using dbMonitor

On this page

To extend the monitoring capabilities of dotConnect for Google BigQuery applications, there is an additional tool called dbMonitor. It is an easy-to-use tool that provides visual monitoring of your database applications. dbMonitor can be used for any kind of application: desktop applications, ASP.NET applications, and Windows services.

dbMonitor performs per-component tracing of database events, such as SQL statement execution, preparation, etc.

dbMonitor has the following features:

ID	Name	Description
1	Events grid	The Events grid displays all traced database events. It provides a brief description, timestamp, duration, and status for each event. Below the grid, four windows are docked in a group: SQL, Parameters, Error, and Call Stack. They display information about the event currently selected in the Events window. You can click a column header in the Events grid to sort the events by that column.
2	Event details	This group of four windows includes: The SQL window displays the SQL statements for the database event selected in the Events window if the event is an execution of SQL code. The Parameters window displays the SQL statement parameters for the database event selected in the Events window if this event is an execution of an SQL statement that contains parameters. The Error window displays information about the error that occurred. The Call Stack window displays the call stack of the function that started the event. You can view the main details of the selected event by switching between these windows. The screenshot above shows the SQL window for the event (this event is an execution of SQL code). To open the window you need, select the corresponding item from the View menu.
3	Processes window	This window displays a list of monitored processes and their statuses. It allows you to choose which process to trace. The Events grid displays events only for the selected process. After the application process is closed, it gets the Terminated status, but its event log is not cleared, so you can still view its information or save it to a file. To remove a terminated process from the list, either right-click it and select Delete Inactive from the pop-up menu, or click it and then click the Delete Terminated Process button on the toolbar.
4	Object tree window	This window, located below the Processes window, displays monitored objects. Objects are organized in a tree with the top-level All Objects node, second-level connection object nodes, and third-level object nodes. The Object Tree window also contains the Pools node that groups connection pools. It allows you to view events for all process objects, for a specific connection, or for a specific object. Just click a node to trace events for this node and its descendants.
5	Call tree window	It contains merged call stacks of the database events for the process. You can use it to filter events by the functions that started them. Just click a function in the call stack tree, and the Events window will display only the events called from that function or its descendants.
	Remote debugging	To use remote debugging for your applications, set the following properties: BigQueryMonitor.Host - to the name or IP address of the computer where dbMonitor will be used. BigQueryMonitor.Port - to the port that will be used for communication between dbMonitor and your application. Then, in the dbMonitor options, set the same port value on the General tab of the Options dialog box. After this, you can run your application and monitor database calls.
	Unicode support	You can monitor applications that use international databases with the help of Unicode support.

During monitoring, you can easily switch between client processes and view the hierarchy of objects being traced.

dbMonitor is designed to affect the monitored application as little as possible.

Monitoring is available at design time as well.

To trace your application with dbMonitor, follow these steps:

Create an instance of the BigQueryMonitor component in your application. You can do this by dropping BigQueryMonitor onto a form from the Toolbox or by creating it manually in code. Only one instance of BigQueryMonitor is needed in the application.
Set the BigQueryMonitor.IsActive property to true to enable monitoring.
Start the dbMonitor application before running your program. If dbMonitor is installed, you can start it from the BigQueryMonitor component designer by clicking the "Run dbMonitor" verb or from the Google BigQuery submenu of the Tools menu.

Optional. To trace your application remotely with dbMonitor, follow these steps:

Perform the steps listed above.
Set the BigQueryMonitor.Host property to the name of the computer where dbMonitor is running.
Set the BigQueryMonitor.Port property to the port number of the dbMonitor application (1000 by default).
Run the dbMonitor application and start tracing.

Optional. You can further tweak monitoring for better performance:

Sending a call stack is a costly operation that can cause performance losses. If you don't need call stacks of the events, it's better to disable call stack sending by setting the BigQueryMonitor.SendCallStack property to false.
You can further improve performance by filtering the events you want to monitor. Specify the event kinds that you want to monitor in the BigQueryMonitor.Filter property. See MonitorEventFilter for information on the available event types.

[email protected]