Skip to content

Releases: tableau/Logshark

Logshark v4.2.3

08 Dec 19:02
3fe1bed
Compare
Choose a tag to compare

This release contains the following changes:

Highlights

  • Tableau Prep plugin. Now users can use this new plugin to quickly and easily analyze their Tableau Prep logs. This plugin is compatible with logs from both Tableau Prep Builder on-prem and desktop versions.

Maintenance

  • Backgrounder: fixed timeout error per user request, workbook tooltip and re-queue job bug were events are not processed in order.
  • Apache: updated regex on Vizql Session ID calc and added more request categories

LogShark v4.2.2

07 Feb 20:21
43e53bf
Compare
Choose a tag to compare

This maintenance release contains the following changes:

Highlights

  • LogShark can now process individual log files (from the same log set) on parallel threads.
  • LogShark no longer publishes [No Data] workbooks to Tableau Server by default. Run Summary now explicitly lists all the workbook that were not published this way.
  • Added support for the 2020.1+ format of Apache logs
  • Added ability to parse service status lines from tabadmin logs

Maintenance

  • Fixed defect where logshark would fail to collect postgres process information for server topology view (config plugin) if there was only one postgres process for a multinode server

  • TabadminController workbook updates

    a. Fixed the missing status events , captured the detailed message
    b. Make outage more visible for Process Status dashboard

LogShark v4.2.1

10 Feb 18:00
6a4c6d0
Compare
Choose a tag to compare

This maintenance release contains the following changes:

Highlights

  • TabadminController plugin (a.k.a TSM plugin). This new plugin extracts information about Tableau Server admin activities (i.e. start, stop, backup, etc.) for servers managed by TSM. Detailed documentation is coming soon!
  • ClusterController plugin now parses and visualizes DiskSpaceMonitor events.
  • When publishing a large workbook to the Tableau Server, sometimes it can take a while to generate thumbnails. LogShark now has a separate setting for publishing timeout. It also handles and reports publishing timeouts differently, as in most cases such timeouts do not mean that the publishing process failed.
  • LogShark now has an ability to add a configurable footer to the description of the project it creates on Tableau Server. Footer text can either be provided as command line --ts-project-description-footer parameter or specified in the config.

Maintenance

  • Config plugin: Server Topology information was not parsed correctly for 2020.3+. Issue is fixed and we also added a few more processes to Server Topology screen.
  • ResourceManager plugin: disk space usage total numbers were reported incorrectly.
  • DataServer plugin: certain JSON lines in data server logs were causing the LogShark run to fail.
  • Hyper plugin: Some large numeric values in logs were causing the LogShark run to fail.
  • Fixed typos and clarified some comments in the Art and Hyper workbooks.
  • Replayer plugin: Two more commands added to skip list.

Docker and macOS

We added instructions on how to do build and run LogShark using Docker to the README file. This should allow to easily run LogShark on any OS, including macOS Catalina!

LogShark v4.2

29 Jul 00:28
Compare
Choose a tag to compare

With this release we've added the following:

Highlights

  • DataServer Plugin. Added a new plugin that parses data server logs and an associated workbook

  • Art Plugin. Art plugin extended to support Desktop logs

  • Moved to .NET Core 3.1 for better performance and memory management

Maintenance

  • Fixed issue with backgrounder plugin producing no results for newer logsets in v4.1.2

  • Added missing test data for end to end tests

  • Better error message if user requested incorrect plugins

  • Better error message if required C++ libraries are missing in Windows

  • ART workbook's Compare Sessions dashboard shows less data by default (so it loads faster initially). Also few improvements to tooltips

  • Also various improvements across multiple existing workbooks

  • Fixes for null reference exception in Replayer plugin

  • Various performance improvements and bug fixes

Logshark v4.1.2

06 Mar 01:41
b22c1cd
Compare
Choose a tag to compare

With this release, the source code for LogShark 4 is now available. In addition to the features listed in the v4.1 release, we've added the following:

Highlights

  • Replayer Plugin. This plugin has been added, but is disabled by default. You can either request it explicitly through command line parameters or change default plugin configuration in the configuration file.

  • Workbook Tags. The Config plugin outputs tags with Tableau Server build and version. If publishing is enabled, these tags will be applied to the published workbooks. Tags can be disabled in the configuration file.

  • Apache Plugin: New fields are extracted from 2020.1 logs.

  • Backgrounder Plugin: Added support for additional formats of subscription information.

Maintenance

  • Hyper Plugin. Changed data type for memory-related fields for the Hyper plugin. These fields have been changed from int to long. If you are using Postgres output, you will need to manually delete or change the data type of the corresponding columns in SQL, as LogShark will not delete or alter schema in your database.

  • Exit Codes. LogShark's exit codes will more accurately reflect whether the run was successful. This is part of an ongoing effort to improve automation and will continue to be refined.

  • Spelling Matters. Misspelling a plugin name in the --plugins parameter will now cause the run to exit with an error.

  • More Configuration Options. Which plugins run by default is now controlled by the configuration file.

  • Various bug fixes and improvements.

LogShark v4.1

07 Nov 19:23
cdb79d5
Compare
Choose a tag to compare

LogShark 4.1 is significantly FASTER and brings back the ability to write to a PostgreSQL database server, as well as a number of other improvements. In this release we are sharing the application as-is and will share the source code in a follow-up release.

Please note, unlike previous release LogShark 4.1 doesn't have an installer. Instead it is shipped as a self-contained application in a zip file (separate zip files for Windows and macOS). Please see Installation and User Guide for more details.

Highlights

  • FASTER!! We have recorded speed gains of at least 10-15x in processing logs. So you are getting your results today!
  • Visualize historic trends. You can visualize historic trends of your logs by appending the run results to previous runs in either PostgreSQL or Hyper output.
  • Custom workbooks. You can now open and see what default templates shipped with LogShark look like, and edit them for your subsequent runs. You can also easily add your own custom workbooks.
  • Detailed run and error summary! One of the issues we have heard is a need for a more detailed log run summary, including info on what lines failed to process and why. No more hunting for errors in LogShark logs!
  • Updated ART workbook. Updated ART (Activity and Resource Tracing) workbook to provide better analysis of CPU and memory utilization for each Vizqlserver activity.
  • Run LogShark from anywhere. LogShark can be added to PATH and executed from any directory.
  • macOS! Yes, you can now run LogShark on macOS (please note that 10.15 Catalina implemented new security features that are currently interfering with LogShark).

Other Improvements

  • Publish to sub-projects on the server. LogShark can now publish into other projects on Tableau Server.
  • Add your own RunID to the workbooks. To help you differentiate between multiple generated workbooks, we have implemented the feature where you can add your own name to the workbooks.
  • Better help text. We added usage examples to the help screen.
  • LogShark's logs in JSON or text format. LogShark's logs (not to be confused with Tableau logs) can be stored in JSON or text format.

Did we mention faster? LogShark 4.1 is seriously faster, and we couldn’t be more proud!

3.0.2

12 Jun 20:25
68d9531
Compare
Choose a tag to compare

The 3.0.2 release contains a couple of updates and fixes as well as a new plugin.

  • Updated Logshark to be compatible with 2019.3 logs
  • Added Activity and Resource Tracing plugin
  • Fixed a bug in Apache plugin that showed up when apache log entries were missing their HTTP verb or content length

NOTE: Please note that you only need hyperd.exe and hyperd_sse2.exe if you want to build Logshark from code on your own machine.

Logshark v3.0.1

22 Oct 16:50
d2f2c48
Compare
Choose a tag to compare

The 3.0.1 release contains a single fix to the ReplayCreation plugin: Updated some JSON keys produced by the ReplayCreation plugin to make the output work properly.

If you're already on the 3.0 release and don't use the Replayer plugin - you don't need to upgrade to this version.

Logshark v3.0

17 Oct 21:24
d3b2166
Compare
Choose a tag to compare

This is the release of Logshark v3.0, a command line utility that you can run against Tableau Server or Tableau Desktop logs to generate a set of workbooks that provide insights into system performance, content usage, and error conditions.

Logshark 3.0 includes numerous fixes and improvements made since the previous release, but the most notable changes are:

  • Support for log sets generated by new versions of Tableau Server up to 2018.2.
  • Run outputs are now saved as hyper extracts instead of PostgreSQL. Not only Logshark no longer needs a dedicated Postgres database, it also runs significantly faster. The results of the Logshark run are now saved as hyper extracts embedded with the workbook (twbx), which enables the vizzes to load much faster.
  • Fixed a number of issues reported both internally and via GitHub.
  • Included optional silent Replayer plugin. Instructions and installation guide can be found on Tableau Community.

If you are a new Logshark user and want information about what Logshark is and how to use it, please see the README file and the installation & user guide.

If you are an existing Logshark user upgrading from Logshark v2.1, recommended steps to upgrade are:

  • Take a backup of Config\Logshark.config file, as it is replaced by upgrade (also Log.config if you made any changes to it)
  • Download and run the v3.0 installer to update your existing Logshark installation in-place.
  • Merge changes from original config file into the new one (don't overwrite the file as there are multiple changes in the structure of the file)

NOTE: Please note that you only need hyperd.exe and hyperd_sse2.exe if you want to build Logshark from code on your own machine.

This software is supplied AS-IS as an open-source community-supported tool under the MIT license. Any bugs or feature requests should be directed to the Logshark Git Issues tracker.

Logshark v2.1

06 Jun 21:15
Compare
Choose a tag to compare

This is the release of Logshark v2.1, a command line utility that you can run against Tableau Server logs to generate a set of workbooks that provide insights into system performance, content usage, and error conditions.

Logshark 2.1 includes numerous fixes and improvements made since the previous release, but the most notable changes are:

  • Support for log sets generated by new versions of Tableau Server (including Tableau Server on Linux)
  • New plugin: Hyper
  • Retired plugin: DataEngine

If you are a new Logshark user and want information about what Logshark is and how to use it, please see the README file and the installation & user guide.

If you are an existing Logshark user upgrading from Logshark v2.0, recommended steps to upgrade are:

  • Take a backup of Config\Logshark.config file, as it is replaced by upgrade (also Log.config if you made any changes to it)
  • Download and run the v2.1 installer to update your existing Logshark installation in-place.
  • Merge changes from original config file into the new one (don't overwrite the file as there are multiple changes in the artifact processors config sections)

This software is supplied AS-IS as an open-source community-supported tool under the MIT license. Any bugs or feature requests should be directed to the Logshark Git Issues tracker.