Skip to content

Releases: billgraziano/xelogstash

Release 1.7.0

04 Jun 11:22
Compare
Choose a tag to compare
  • Update to GO 1.16.5
  • Update dependencies

Release 1.6.2

28 Mar 14:54
Compare
Choose a tag to compare
  • Bump to GO 1.15.8
  • Rewrite logstash writer to better handle intermittent issues
  • Clean up logging

Release 1.5.5

03 Feb 13:26
Compare
Choose a tag to compare
Release 1.5.5 Pre-release
Pre-release

Improve handling NULL state files

Release 1.5.4

17 Dec 20:24
Compare
Choose a tag to compare
  • Handle closing a nil connection

Release 1.5.3

14 Dec 13:30
Compare
Choose a tag to compare
Release 1.5.3 Pre-release
Pre-release
  • COALESCE DEFAULT_DOMAIN function to better support Linux

Release 1.5.1

29 Sep 13:09
Compare
Choose a tag to compare
  • Minor memory usage clean up

Release 1.5.0

02 Sep 12:48
Compare
Choose a tag to compare
  • Add a .vscode directory in the samples with extensions and file mapping support
  • Fix the git commit information in the linux build
  • Fix the subdirectory in the linux build
  • Update the README for first-timers
  • Add the server name to the polling message (in addition to being in the field)
  • macOS should work now but you'll have to build it yourself on macOS.

Release 1.4.4

31 Aug 12:11
Compare
Choose a tag to compare
Release 1.4.4 Pre-release
Pre-release
  • Improves support for trusted connections in Linux. See Linux Support for more details.
  • Added the login_failed field. This is populated for errorlog_written (logon) events and error_reported events whose error number indicates a login failed event. Filter Kibana for the existance of this field. See below for more details.
  • Unfortunately, adding trusted connections in Linux broke macOS (darwin) support for a bit.
  • Fix logging bug

Release 1.4.0

18 Aug 13:04
Compare
Choose a tag to compare

This application now reads past invalid offsets. The most likely cause of invalid offsets is that this service stopped or the files rolled over so fast that the file and offset are no longer valid. In both cases, the extended event files rolled over and the events no longer exist. Previously this application would log the error and wait so we could investigate and fix. Meanwhile, more events were being missed. Now it just logs the error and tries to find the next valid event for the extended event.

Release 1.3.3

13 Aug 13:16
Compare
Choose a tag to compare
Release 1.3.3 Pre-release
Pre-release
  • Fix bug that allowed connections to leak when polling a server that didn't exist for the first time
  • Clean up the versions in replacements and logging
  • Deprecate GITDESCRIBE. Please see the README.