xelogstash

Send SQL Server Extended Events to Logstash, Elastic Search, or JSON

OTHER License

Stars
26

Bot releases are visible (Hide)

xelogstash - 1.3.0-Linux and Darwin support

Published by billgraziano about 4 years ago

This includes Darwin and Linux support. The code is in the "linux" branch. The ZIP file holds all three executables. I'll see about better archives for each OS next.

The Windows support is good but Darwin and Linux are experimental.

xelogstash - Release 1.2.1

Published by billgraziano about 4 years ago

  • Bug fixes
xelogstash - Release 1.2.0

Published by billgraziano over 4 years ago

  • Supports adding filters (see Filters in the Application Settings)
  • Parse Error Log events into individual fields
  • Configuration files are split into two. Sources can now be split out into a separate file named sqlxewriter_sources.toml. NOTE: This requires that configuration files are named sqlxewriter.toml and sqlxewriter_sources.toml.
xelogstash - Release 0.92

Published by billgraziano over 4 years ago

  • Coalesce multiple file change events into a single event. This behaves much better if you're editing the file while it's running. I still don't suggest this though.
  • Better handle errors where logstash stops responding
xelogstash - Release 0.91

Published by billgraziano over 4 years ago

  • Hot reload the TOML files on file save
  • Bug fixes
xelogstash - Release 0.9

Published by billgraziano over 4 years ago

  1. sqlxewriter.exe runs as a service
  2. Added metrics page to see a count of events read and written
  3. Log memory use every 24 hours
  4. Added retry logic for sinks
  5. Logging to a JSON file suitable for Filebeat
xelogstash - Release 0.45-alpha

Published by billgraziano almost 5 years ago

  • Convert to JSON for application logging
  • Removed the applog section and functionality. Use FileBeat to write the JSON application log into ELK.
  • FileSink now write to a single shared file for all targets that is rolled hourly. This is designed to be processed by FileBeat.
xelogstash - Release 0.44

Published by billgraziano almost 5 years ago

  • Reduced the default worker count to the core count
  • Better logging of the application version inside the app
  • Added two sample extended event sessions
xelogstash - v0.43

Published by billgraziano almost 5 years ago

  • Added sample extended event sessions and cleaned up sample TOML files
  • Cleaned up logging
  • Improved reliability of sending to logstash using TCP
xelogstash - 0.41-beta

Published by billgraziano about 5 years ago

Include support for sp_server_diagnostics_component_result

xelogstash - v0.40-beta

Published by billgraziano about 5 years ago

The beta release has a number of significant changes:

  • BREAKING: The TOML file format has changed. Please review the README.
  • Adds support for writing events to files so they can be processed by FileBeat
  • Improves support for writing directly to Elastic Search
  • Adds an mssql_product_level field with the full build number.
xelogstash - Release 0.38

Published by billgraziano about 5 years ago

  • Better logging
  • Remove lock file later in program
  • Explicit shutdown of HTTP server
  • Fix TCP sends to avoid too many outbound connections. This causes issues when a session gets behind and it fails with a "bind" error when trying to catch up.
xelogstash - Release 0.36

Published by billgraziano over 5 years ago

  • Includes early support for writing directly to Elastic
  • Added a look_back field to only process the most recent events
  • Improved build versioning
xelogstash - Release 0.33

Published by billgraziano over 5 years ago

This is mostly extra logging in bad situations and error handling to avoid those situation.

xelogstash - Release 0.29

Published by billgraziano over 6 years ago

Added lock file to prevent the application from running twice. The lock file is based on the TOML file name.

xelogstash - Release v0.26

Published by billgraziano over 6 years ago

  • Added an exposed metric for the total number of events read even if they aren't processed. This helps to check if the application is making progress.
  • Added an option to exclude SQL Server 17830 errors
xelogstash - Release v0.24

Published by billgraziano over 6 years ago

  • Added per session counts to the exposed metrics
  • Added NOLOCK to the job history query
  • Added a sequence_value to the application log. This is useful for sorting the application log messages.
  • Switched query_hash to a string as it was overflowing
  • Only lower-case the substitutions (ex. $(EXE)) rather than all adds, copies, moves so we can better pass tokens.
  • Added utilities to testing sending a JSON file and test sending a small JSON snippet
  • Added options to start and stop event processing at specific times. This is mostly useful for testing.
xelogstash - Release 0.21

Published by billgraziano over 6 years ago

  • Added more debug level logging
  • blocked process event is now a warning
  • Added flag to ignore sessions for a source so we can just grab agent jobs for SQL Server 2008 servers
  • Add option to expose a web interface while running to see internal metrics
  • The default config file name is now based on the name of the executable
xelogstash - Release 0.20

Published by billgraziano over 6 years ago

  • Non-existent sessions no longer issue a warning
  • Handle sessions that aren't stored in the SQL Server LOG directory
  • Add a command line /log parameter to write to a local log file
  • Improved error handling and logging
  • Moved the "status" files to the "xestate" directory. PLEASE test this carefully.
  • Added a /debug flag that writes additional information.
  • Increased the default workers from the number of cores to 4 * the number of cores.
xelogstash - Release 0.17

Published by billgraziano over 6 years ago

  • Agent jobs have more granularity in how you import them. Instead of true/false, you can now import "all", "none", or "failed". If you choose all, they now import progress reports too.
  • The logic to determine error vs. info for Agent jobs is improved.
  • Better error handling if you create a source without an "fqdn".
  • Better error handling if you enter a non-existent SQL Server.