What's new in ErrorTracker 2.7 Server
Nov 14, 2023
- Users can now be given read-only access to any project.
- Web Push notifications are now sent in 5-second batches, up from 1-second.
- Error emails are no longer sent if the connection is lost while reading an event submission body.
New in ErrorTracker 2.6 Server (Nov 2, 2023)
- Fixed a bug where events that are dropped as duplicates of another event were still sent into the notification queue for the root folder, even if they would have been filtered into another folder. Duplicate events are no longer notified about.
New in ErrorTracker 2.5.1 Server (Sep 13, 2023)
- Updated the HTTP server module and fixed a bug where the Wallpaper endpoint delivered an invalid HTTP 304 response.
New in ErrorTracker 2.4.1 Server (Aug 4, 2023)
- Updates to embedded web server.
New in ErrorTracker 2.4 Server (Jun 14, 2023)
- Added search functionality to the Filter List and Filter Properties pages, with options to use either Regex search or SQL Full Text search.
New in ErrorTracker 2.3.1 Server (May 6, 2023)
- Added admin-configurable setting postgresCommandTimeout with default of 900 seconds, up from standard command timeout of 30 seconds. This should help when executing extremely large SQL commands such as moving tens of thousands of events into a folder.
New in ErrorTracker 2.2.2 Server (Nov 30, 2022)
- Fixed bug where advanced search failed if using "All conditions must match" along with conditions testing the values of 2 or more Tags.
New in ErrorTracker 2.2.1 Server (Aug 10, 2022)
- Fixed broken ability to rename folders.
New in ErrorTracker 2.2 Server (Jun 30, 2022)
- Event context menu now has an option "Copy to other project" which submits a copy of the selected events to a project of your choice.
- Client Version Remains at 1.1
New in ErrorTracker 2.1.1 Server (May 18, 2022)
- Web server update to improve robustness slightly.
New in ErrorTracker 2.1 Server (May 10, 2022)
- Basic search functionality now uses SQL Full Text Search, and searches the Message, EventType, SubType, Color, and Date fields, and additionally searches all of each event's tag values in order to provide a more useful basic search.
- Advanced search is now implemented using SQL so that most queries will run significantly faster compared to loading the entire project's event and tag tables into web app memory to evaluate the conditions.
- To facilitate the above changes, the database schema for projects has been updated to version 7 and will be slow to start for the first time on established systems due to creating full text search indexes.
New in ErrorTracker 2.0 Server (Apr 20, 2022)
- Project databases no longer use SQLite, instead using PostgreSQL.
- A PostgreSQL server must be installed and configured with Error Tracker 2.x before it will function.
- See "Configure PostgreSQL" button in Service Manager GUI.
- Replaced sqlite-net with Npgsql and PetaPoco libraries.
- PetaPoco source was slightly modified for use in ErrorTracker, modifying the caching functionality in PocoData.cs. Otherwise if using the unmodified PetaPoco library, and you use more than one project in ErrorTracker, the databases will be mixed up.
- Added "Migrate From SQLite" dialog to Service Manager GUI which handles migrating old databases.
- Added inline documentation to Admin -> Settings. It is no longer required to look at the wiki on github to understand all the settings.
- Added "Backup Database" and "Restore Database" functions to the Service Manager GUI.
New in ErrorTracker 1.9.0.1 Server (Mar 25, 2022)
- Added automated compressed db backup capability. Requires 7zip command line app, which is included and preconfigured for Windows.
- Improved thread safety of database code because I really don't trust the sqlite-net library very much.
- Fixed a bug where exceptions were not rethrown if they occur when adding an event and running filters.
- Fixed DB migration trigger which wasn't updated properly in past releases, resulting in the harmless recomputation of event hashes at every app startup.
- Updated some dependencies.
- 7zip is now run at BelowNormal priority when compressing db backups.
New in ErrorTracker 1.8.1 Server (Aug 30, 2021)
- The web server can now log additional information for debugging purposes (see settings webServerVerboseLogging, webServerRequestLogging).
New in ErrorTracker 1.8 Server (Jun 21, 2021)
- Expired push subscriptions are now deleted automatically.
- Service start/stop is now logged to the log file.
- Fixed a bug where event lists could load out of order, causing a loss of synchronization between the folder browser and the event browser.
- When deleting a folder, push notification subscriptions for that folder are deleted too.
- Fixed "Filter condition" being logged when "Filter action " was intended.
- Fixed "Filter condition" being logged without a space before the filter condition ID.
- Misc code and dependency cleanup
New in ErrorTracker 1.7 (Feb 20, 2021)
- Improved push notifications so their titles include the project name and clicking them brings you to the event they are related to. When multiple events are combined into one notification, clicking the notification may bring you to a less-specific location.
New in ErrorTracker 1.6 (Jan 5, 2021)
- Added Web Push notifications of new events on a per-folder basis. Requires service worker to be enabled in settings, a web browser compatible with Web Push, and HTTPS.
- The systemName setting will be regenerated upon app startup if it is null or whitespace.
New in ErrorTracker 1.5.1 Server (Oct 6, 2020)
- Fixed a bug where tag values were truncated at the first NULL character when being inserted into the database, such that the tag values could be different (longer) during initial event filtering.
- Certain special characters in Event text field values and Tag Keys/Values, such as NULLs and horizontal tabs, are now converted into visual glyphs.
- Fixed a bug where an "All conditions must match" filter didn't require at least one condition to be met.
- Improved verbose submit logging.