FB TraceManager 2 - Documentation

History of FB TraceManager

History of FB TraceManager

Previous topic This is the last topic  

History of FB TraceManager

Previous topic This is the last topic  

February 15, 2012 - v2.5.0.34

 

Enhancements:

 

Per-database monitoring capabilities including header page monitoring and Firebird MON$ tables integration. See Database Monitoring. #0000235
Database views for easier access to query logon/logoff trace data information. See What's new in V2.5. #0000229
Allow to specify a trace column definition file in the trace project. #0000230
More appealing way to manage trace session options for an active trace session by using flyout tool panels. #0000232
Flyout toolbar panel states are now persisted. #0000253
Attempt to make FB TraceManager more Firebird 2.5.1 friendly, due to http://tracker.firebirdsql.org/browse/CORE-3636. Not entirely sure if this works reliably. #0000255
Increase page buffers value of the FBTM database to 1024. Applies only to new installations. Feel free to adjust the page buffers value for your installation as needed. #0000260

 

Bug fixes:

 

Bug fixed: Refreshing the registered server area (e.g. when editing a server entry) will loose the connected state of servers. #0000234
Bug fixed: FBTM database metadata update might fail, when there are others connections active. Now there is a check in-place, that a metadata update is only executed, if there are no other active connections on the database. #0000256
Bug fixed: Exception "A component named tsStartedProject<N> ..." when starting a trace session. #0000259

 

 

December 20, 2011 - v2.0.8.5

 

Enhancements:

 

Purge strategy for raw and parsed trace data implemented to allow FB TraceManager running in 24x7 scenarios. More information on the new project-based options Raw Max Lines, Parsed Max Rows and Parsed Purge Rows is available in the Trace Data Visualization section. (#0000202)

 

Bug fixes:

 

Bug fixed: "Access violation at address 00000000. Write of address 00000000." in random situations. (#0000200)
Bug fixed: FBTMLoggerSvc: Parsed trace event is always one event behind. (#0000201)

 

 

November 29, 2011 - v2.0.7.1

 

Enhancements:

 

Support for EXECUTE_BLR trace event. (#0000195)

 

Bug fixes:

 

Bug fixed: Main window state is always maximized, thus ignores the previously used position and size. (#0000194)

 

 

November 21, 2011 - v2.0.6.1

 

Enhancements:

 

None

 

Bug fixes:

 

Bug fixed: Parser: Execution time in EXECUTE_PROCEDURE_FINISHED processed wrongly. (#0000185)
Bug fixed: Parser: Number of reads/writes etc ... in COMMIT_RETAINING not processed. (#0000186)
Bug fixed: Parser: Number of reads/writes etc ... in ROLLBACK_RETAINING not processed. (#0000187)
Bug fixed: "Number of records fetched" is stored as -1 when it should be 0. (#0000188)
Bug fixed: Another potential AV upon stopping a busy trace session. (#0000189)
Bug fixed: Trace data storage transacion isn't committed when stopping a trace session via the trace session list. (#0000190)

 

 

November 18, 2011 - v2.0.5.0

 

Enhancements:

 

None

 

Bug fixes:

 

Bug fixed: Problem in parser handling parameters and detailed statistics for EXECUTE_PROCEDURE_FINISH. (#0000182)
Bug fixed: Problem in parser handling parameters and detailed statistics for EXECUTE_STATEMENT_FINISH. (#0000183)
Bug fixed: Problem in parser handling number of reads/writes etc. for EXECUTE_PROCEDURE_FINISH. (#0000184)

 

 

November 15, 2011 - v2.0.4.0

 

Enhancements:

 

None

 

Bug fixes:

 

Bug fixed: Memory usage steadily increases even without visualization enabled. E.g. in the logger Windows service or in the application if "Paused" and "Dismiss when Paused" = ON in the visualization, thus memory usage shouldn't increase in this case. This makes the Windows logger service FBTMLoggerSvc capable to run 24x7 without significant memory usage. The fix also affects FB TraceManager, because less memory is used when adding a lot of trace events to the raw and parsed output. (#0000181)

 

 

November 14, 2011 - v2.0.3.5

 

Enhancements:

 

New event rule type "OnExecuteApplication" for executing an application has been added in the Event Processing module. (#0000175)
New event rule type "OnPlaySound" for playing a (system) sound has been added in the Event Processing module. (#0000176)

 

Bug fixes:

 

Bug fixed: Possible crash in the Trial Edition after exceeding the max. number of allowed parsed trace events. (#0000177)

 

 

November 10, 2011 - v2.0.2.8

 

Enhancements:

 

Project-based "re-sort" option for re-sorting newly added parsed rows automatically. (#0000155)
Allow to set footer band column value as column regex filter. (#0000156)
In query result set (used in Browse, Reporting, Analysis): Show real CLOB/Memo field content instead of WIDEMEMO. (#0000167)
Improved application responsitivity with busy trace sessions. (#0000169)
Replaced memory manager which results in overall slightly improved performance. (#0000170)
Project-based "Dismiss when paused" option to remove received trace events from the queue when visualization is paused. (#0000173)

 

Bug fixes:

 

Bug fixed: Regex filter in parsed grid fails for input values containing regex filter escape characters. (#0000157)
Bug fixed: Another race condition when post-processing certain event types leads to trace session abort. (#0000158)
Bug fixed: In Project Wizard: Trace configuration isn't stored when clicking on Finish without visiting the last wizard page. (#0000159)
Bug fixed: In Analysis Wizard: "Finish" button isn't enabled after entering a SQL statement. (#0000161)
Bug fixed: Crash when closing the application while running trace sessions are busy. (#0000162)
Bug fixed: Occasional "List index out of bounds (-1)" error message with busy trace sessions. (#0000163)
Bug fixed: Post-processing trace events produces garbage while receiving trace data which leads to exception when log to database is enabled and more. (#0000164)
Bug fixed: "List index out of bounds (-1)" error message when working with a selected project, trace session after refreshing the list. (#0000165)
Bug fixed: Double-clicking the module (Browse, Reports, ...) menu items instead of a single-click leads to an exception. (#0000166)
Bug fixed: FBTMLoggerSvc2: Stored session name is not the logger service session name. (#0000168)

 

 

November 7, 2011 - v2.0.1.1

 

Enhancements:

 

None

 

Bug fixes:

 

Bug fixed: In case of an application error, the application crashes instead of showing a detailed exception dialog (stack trace). (#0000147)
Bug fixed: The exception stack trace file (.elf) isn't placed in the user's application data directory. It now goes into "C:\Users\<account>\AppData\Roaming\FB TraceManager 2" or "C:\Users\<account>\AppData\Roaming\FB TraceManager 2 Lite". (#0000148)
Bug fixed: Memory leak per received trace event. (#0000149)
Bug fixed: Rare access violations with certain processed trace event types. (#0000150)
Bug fixed: Minor memory leaks caused by the Reporting, Analysis and Event Processing module. (#0000151)
Bug fixed: Number of allocated threads doesn't decrease when stopping a trace session. (#0000152)
Bug fixed: Crash when stopping a busy trace session. (#0000153)

 

 

October 31, 2011 - v2.0.0.9

 

Enhancements:

 

Improved multi-threading capabilities. Especially in the area of synchronizing the GUI with received trace data from background worker threads has been re-written. This should consume less CPU and should not starve the main GUI thread. In general, the application should be more responsive when running several trace sessions at the same time now. (#0000105)
Minimize to tray option to be found in the Settings. (#0000107)
Ability to duplicate a server entry. (#0000108)
Support for regular expression filters in trace session and project list. (#0000109, #0000110)
Per project option to define the GUI refresh interval (milliseconds) in the newly implemented multi-threading model. (#0000112)
The raw output visualization has been improved a lot. (#0000111)
- Line number
- New trace event line can be highlighted with a custom background color
- SQL Syntax-Highlighting
- Trace event type (PREPARE_STATEMENT, CLOSE_CURSOR ...) keyword highlighting
- Trace event raw data folding to collapse/expand trace event data
- Support for bookmarks to navigate to user-definable locations easily
Option in Register Server wizard to auto-connect upon program start. (#0000114)
Support for all parsed grid columns when copying content to clipboard (context-menu) and not only SQL and execution plan. (#0000116)
Append "- Copy" text in certain fields in various wizards when duplicating an entity (project, report, analysis ...). (#0000118)
Context menus in report and analysis manager tree view added. (#0000119, #0000120)
Footer band in parsed data grid with column-based aggregate functions on numeric columns. (#0000123)
Locate line in raw data output for a given parsed trace event by double-clicking (or context-menu) a row in the parsed trace data grid. (#0000125)
Temporary queue received trace data/events in case of paused visualization and process upon resume. This makes the "Add invisible row when paused" option obsolete, thus it has been removed. (#0000126)
"Cancel" button in transaction active confirmation dialog when closing a trace session tab to cancel closing the tab. (#0000127)
GUI improvement: Replace splitter with flyout tool panels were applicable. (#0000132)
Added units ([ms], [pages]) in parsed grid column header caption for certain columns (e.g. Execution time ...). (#0000135)
Setting a filter in parsed trace data grid from column values in the selected row. (#0000139)
Show image/icon in header of parsed trace data grid in case of a filtered column. (#0000140)

 

Bug fixes:

 

Bug fixed: Fixed a bug where the parsed grid output and persisted trace events are always one event behind the raw output. (#0000106)
Bug fixed: Fixed a rare race condition when running multiple trace sessions simultaneously. (#0000113)
Bug fixed: Rare occasion where a newly added parsed grid row got a white text color. (#0000117)
Bug fixed: Potential problem when detecting the Firebird version upon server connect. (#0000121)
Bug fixed: Problem with parser for an unauthorized attach database event, as there is no ROLE information in the trace data included. (#0000122)
Bug fixed: Rare race condition when pausing visualization while trace data is received/processed. (#0000128)
Bug fixed: AV when deleting an event rule which is currently in edit mode. (#0000131)
Bug fixed: Parser has problems when post-processing certain event types (e.g. COMPILE_BLR). (#0000134)
Bug fixed: In case of an application error, the application crashes instead of showing a detailed exception dialog (stack trace)

 

 

July 22, 2011 - v1.6.0.10

 

Enhancements:

 

Windows service based logger application (FBTMLoggerSvc2) has been implemented. It's included in the download package for registerd customers only. Initially it is a trial version and needs to be licensed separately. Check out the FBTMLoggerSvc - Windows Service section. (#0000035)
Administration of Windows service based logger has been added to the project wizard. Check out the FBTMLoggerSvc - Getting Started section. (#0000036)
Make trace-session based options (log to database, commit interval ...) available per project. (#0000029)
Project-based default regex filter values. (#0000032)
In the server-based project list: Button Browse Trace Data to jump/navigate to the Browse module for the selected project. (#0000034)
Optimize memory usage in trace data parser. Allocates and frees memory more efficiently now. (#0000040)

 

Bug fixes:

 

Bug fixed: FBTM database metadata update sometimes fails. Querying the database version is now properly closed before executing scripts. (#0000033)
Bug fixed: Memory leak in trace data parser, which results in out of memory exceptions when running FB TraceManager 2 for a while with active trace sessions. As each trace session holds it's own trace data parser instance, things are getting even worse with an increasing number of active trace sessions. (#0000039)
Bug fixed: Minor memory leaks. (#0000050)

 

 

May 23, 2011 - v1.5.2.2

 

Enhancements:

 

Option to automatically start trace sessions upon server connect. (#0000015)
Multi-select in project grid to enable start/delete of multiple projects. (#0000016)
Multi-select in trace session list to resume/suspend/stop multiple trace sessions. (#0000017)
Clear regex filter functionality implemented. A button / context-menu item in the parsed trace data grid area allows to clear a defined regex filter. (#0000018)
Confirmation dialog to commit active log database transaction in case of closing the trace session tab sheet. (#0000019)
Allow regex filter on # column in parsed trace data grid. (#0000020)
Show "Finish" button in project wizard in all wizard pages. (#0000026)

 

Bug fixes:

 

Bug fixed: Rare AV when closing FB TraceManager 2 with active trace sessions. (#0000014)

 

 

March 21, 2011 - v1.5.1.3

 

Enhancements:

 

"Disable Event Processing" option in Parsed tab when running a trace session. (#2311)
Active/Deactivate all event rules in one step for a particular project. (#2312)
Persist currently selected tab information in various places across the application. (#2313)

 

Bug fixes:

 

Bug fixed: Alert window caption still shows "Firebird Trace Manager" instead of "FB TraceManager". (#2310)
Bug fixed: Access violation when closing FB TraceManager 2 in case an event processing alert window has been shown before. (#2313)

 

 

November 30, 2010 - v1.5.0.29

 

Enhancements:

 

Due to a trademark issue on the "Firebird" term in the product name, we have renamed our product from Firebird Trace Manager to FB TraceManager 2. This change also includes the group name in the Windows start menu, the location of FB TraceManager 2 user files (database, reporting/analysis files etc.) and more.
Event processing facility to execute actions on user-defined conditions on parsed trace data. Check out the new Event Processing section. (#2239)
Support for services trace events. This allows to configure, receive, parse and persist services trace events (backup, restore, get server log, etc.). Check out the Register Project wizard for new services related trace options. New event names introduced in parsed trace data: ATTACH_SERVICE, START_SERVICE, DETACH_SERVICE, QUERY_SERVICE with specific detailed data in columns starting with SERVICE_. (#2235)
Small icons and list style for displaying registered servers. This makes working with a larger number of registered servers easier. (#2234)
Preserve data grid states (visible columns, column position, column width, sorted by etc.) after program restart. (#2281)
Allow copy SQL and execution plan text from parsed trace data grid into clipboard. A new "Copy" menu item with sub-menu items is available in the parsed trace data grid context menu. (#2291)
Enable selecting visible columns in parsed trace data grid including a way to save/load column definition presets. A new "Visible Columns" menu item is available in the parsed trace data grid context menu. (#2292)
Column-based case-sensitive/insensitive regular expression filter ability in parsed trace data grid. (#2293)
New option "Add invisible rows when paused" to configure if invisible rows should be added in case of "Paused" state for parsed trace data grid has been added. (#2294)
Dataset navigator buttons for each data grid in Browse module. (#2299)
More intelligent logic with user dialogs in case of failed server registration. (#2304)
Choose a different server when creating, duplicating a project. (#2305)

 

Bug fixes:

 

Bug fixed: Disconnecting from server doesn't stop trace sessions started by FBTM. (#2232)
Bug fixed: Closing FBTM doesn't stop trace sessions started by FBTM. (#2233)
Bug fixed: Raw output isn't get stored, if LogToDatabase option in Parsed tab isn't set. Storing the raw output must be independent of this setting. (#2243)
Bug fixed: Import fails, if trace data is wrapped in memo component. (#2278)
Bug fixed: Access violation upon receiving trace data when parsed trace data grid isn't sorted by a column. (#2282)
Bug fixed: Access violation parsing trace data with statements including date literals. (#2287)
Bug fixed: Allow keyedit in port spinedit in server wizard dialog. (#2290)
Bug fixed: Failed database transactions are rolled back without re-raising exception. (#2295)
Bug fixed: Installer waits until FBTraceManager.exe terminates, if the "Run ..." option has been chosen in the postinstall area. (#2296)
Bug fixed: Typo in "Nubmer of writes" column header caption in parsed trace data grid. (#2301)
Bug fixed: Malformed string exception when storing trace data with special character (e.g. Ø) in the FB TraceManager 2 database. (#2303)

 

 

October 4, 2010 (Ready for the Firebird 2.5 launch) - v1.0.1.5

 

Enhancements:

 

Firebird 2.5 RC3/Final compatibility. The trace data parser failed due to a minor change in the raw trace output. (#2219)
Firebird 2.5 Embedded 32-bit Final is now included (previously Beta/RC). (#2225)
Make use of the Windows user-specific application directory for storing FBTM data. E.g. on Windows 7: C:\Users\<account>\AppData\Roaming\Firebird Trace Manager. (#2214)
Store client character set in parsed data in the FBTM database. (#2220)
Added an option for keeping the selection in the parsed trace data grid. (#2222)
Sticky first column in parsed data grid. (#2223)
If parsed trace data output is paused, rows are now still added, although invisible. Removing the selection of the Paused checkbox makes all invisible rows visible again. (#2224)
Improved usability by adding context menus to the various grid views. (#2226)

 

Bug fixes:

 

Bug fixed: Newly inserted parsed row data doesn't necessarily fulfill the currently used grid sort order. (#2221)

 

 

February 10, 2010 - v1.0.0.19 (Initial Release)