This Tracing SQL Store Component contains a Trace DAO implementation that can be used by the trace engine to store trace messages in a database.
The configuration options are found below in this document.
Requirements
This component persists data in a database, that must be provided. See platform support for the supported databases.
Installation
In order to use this component, the trace-sql-store profile must be active. More information on how to configure the application using Spring Profiles can be found here : Component configuration with Spring Profiles.
In order to use this component, make sure to have the BlueriqComponentTracing.dll in the /bin directory of your .NET webapp installation
Configuration
Database
Scripts to create the required database content are provided for the following databases:
The Trace SQL Store component is using the trace datasource to store data.The trace datasource can be configured using JDBC or JNDI.
Using JDBC datasource: This can be configured in the application-externaldatasources.properties file. When configuring external datasources, the externaldatasourcesprofile should be enabled.
Using JNDI datasource : this can be configured in the application-jndidatasources.properties file When configuring JNDI datasources the jndidatasourcesprofile should be enabled.
Configuring the datasource from the Development Dashboard Go to Settings Widget → Datasources tab → On the left side menu : select Trace SQL Store datasource. The same properties are available for configuration as from the properties file. Make sure the corresponding profile is enabled (externaldatasources or jndidatasources)
Hibernate settings These settings are done for each datasource type in the corresponding properties file, as in the examples above.
Configuring the database connection for the Tracing SQL store component in .NET is done by adding a connection configuration to the
Unable to render {include} The included page could not be found.
The Tracing SQL store component looks for a database connection named "TraceDao" so make sure that this name is used in order to configure the Trace SQL Store properly.
All necessary DLL files the Trace SQL Store component depends on can be found in the /bin directory of the .NET webapp ZIP file.
Performance
The performance impact of the Trace SQL Store is minimal when used normally: to write trace messages to the database.
It is also possible to use the Trace SQL Store to query the trace engine database, like the timeline container does. The Trace SQL Store offers good performance as long as the result set is limited. For large scale analysis, when summaries or aggregates are desired, the Trace SQL Store is not recommended because it is primarily designed to return a list of trace entries. For these scenarios it is recommended to use SQL (or HQL) to query the database.