Can we remove the ART data from the Value section? It's so much harder to read the logs with that extra material in the way.

The highlight filter and opened files should remain the same for the next session. This is how other log viewers work and they save a lot of time. Thanks for the software!

There a new top level key in Tableau logs, which is "a", I think it stands for "activity". TLV is currently unable to display this information. This would probably be a new column (just like "Time" and "Value" are now).

Example of event:
{"ts":"2017-11-15T17:05:09.898","pid":50992,"tid":"bf10","sev":"info","req":"-","sess":"-","site":"{5843357A-1609-4CB9-BBF1-C4307BBCC217}","user":"-","k":"end-ds-connect-data-connection","a":{"depth":3,"elapsed":0.064,"end":"2017-11-16T01:05:09.842Z","id":"P/////U30nQP/////30IOX","name":"ds-connect-data-connection","res":{"alloc":{"e":"4.42e+03","i":"4.67e+06","ne":50,"ni":54037},"free":{"e":"3.11e+03","i":"1.58e+06","ne":33,"ni":9296}},"rk":"success","rv":"","sponsor":"J+JTXBxiUHGP////+0fkqw","type":"end","view":"","workbook":""},"v":{"caption":"Airport","elapsed":0.064,"name":"Airport"}}

One tricky thing is that "a" has nested objects and the the collapsing/expanding might conflict with Value (how to display both?)

I have large query trees that I'd like to optimize. (in some cases exceeding 500k nodes, as known from the relevant error message)
when trying to visualise these, I click the button and nothing happens (i suppose due to the excessive size).
Is this expected?

Stuff doesn't work, I blame Alvin

From time to time, I am using simple ad-hoc scripts to search for more complicated patterns in log files. E.g., recently I had to write a small script which gave me a list of all threads which did acquire locks but did not release them again. I keep those scripts very simple, and they usually output only line numbers of interesting events.

It would be perfect if I could enter the obtained line number in a Go to line dialog.
Usually, I would just go ahead and implement that feature. However, Go to line is usually associated with the keyboard combination Ctrl+G - and this one is already used for the highlight dialog.

Hence, I wanted to start a discussion first: Do you consider Go to line useful? Do you think we should reassign Ctrl+G to Go to line and find some other shortcut for Highlight?

If I attempt to name highlight filter something like "end-query" then I get following error:
Only alphanumeric characters and underscores are allowed.

That name is used as a file name so let's allow everything that file system can handle.

Got a request to port back "split by" functionality from original TLV.
Any takers?

Log splitting
To make it easier to analyze large complex log files, they can be split into multiple views in TLV based on a single value or all values of one of the columns. Currently log splitting is only possible by columns TID, Request, Session, Site, User and Key.

To split current view by all values of a selected column click on the menu command "split by...", which will display a dropdown menu where you can choose which column to split the view by. This will create a new tab window for each value of the chosen column and those tabs will only contain records that have one of the selected column values.

Searching does not respect highlight only mode, occasionally displaying search results from non-displayed entries.

You need to be using a Mac and the "Native" theme to see this.

1. Open TLV
2. Open any log file
3. Open the "Preferences..." window
   =>Notice how the style and color changes on the main window, a hybrid of light and dark elements. Change is undoable unless you re-start TLV
   

Very often I look at log files either in archives or Splunk i.e. where I do not get a direct access to a file path.
I'd like to be able to select log lines, copy them to clipboard and load the up to TLV from clipboard.

Tableau can do it why can't you? :)

I'm unable to install Qt due to missing Xcode and it's command tools - should add a sentence for that.

When attempting to visualize a query while using TLV through Remote Desktop, the window that should contain the graph will pop up, but its contents will be plain black. Image attached below to illustrate. This is while RDPing to Windows Server 2008R2 from a Windows 10 machine. The same behavior is observed in Windows's default RDP client as well as Remove Desktop Connection Manager 2.7.

Let me know if any other information can help you on this!

The find window should not close because multiple instances of a string could exist and this finds just the first ocurrence. It should work similarly to the Microsoft Word search window.

Allowing user to select sorting by ID, Time, or Elapsed would be a nice addition

Can't build on Windows 10. I've tried all methods. nothing works just get errors

Happening in the latest TLV (from Luis's click once installer).

Steps to repro:

1. Open a log entry. Notice that wrap text is checked by default
2. Uncheck the wrap text option
3. Close the log entry
4. Open the same or another log entry

Expected: Wrap text is disabled
Actual: Wrap text is enabled again (by default)

While running qmake -spec macx-clang -Wall ../src/tableau-log-viewer.pro on mac terminal getting 29 warnings and 12 errors generated

Untitled document.docx

I have uploaded the errors I am receiving,. Can you please help me on this ?

Hello,

I'm investigating TLV as a possible solution to quickly parse Tableau Server Logs.

It's seems very useful with handy options existing out-of-the-box.

I've noticed that the column "value" also contains the time info; if I also put the check to display the time column the rows for the column are empty so the data is not splitted accordingly (please see the attached image).

How can I solve this?

Thanks,
Bogdan

When the log contains large 64bit integers, they do not get correctly displayed. The last digits differ from the actual value.

Given the example log line:
{"ts":"2018-11-28T17:33:01.230","pid":43075,"tid":"70000dbe3000","sev":"info","req":"-","sess":"10483","k":"large-integer","v":{"some-id":9223372036855065056}}
TLV will show "some-id: 9223372036855064576"

This is probably due to parsing the number as a double first and loosing precision on the way. I am not sure if the underlying JSON parser supports the whole range of int64 and this is a TLV issue or if this is a limitation of the JSON parser itself.

Horizontal scrollling is not working and makes difficult to read big strings.

Repro steps

1. Open a text file in TLV
2. Delete said file in explorer (or something)
3. Click "Refresh" button in TLV

Observed

crash

Expected

no crash

Which might scare people when qmake throws warnings:

qmake -spec macx-clang CONFIG+=x86_64 -Wall ~/Development/tableau-log-viewer/src/tableau-log-viewer.pro
WARNING: /Users/russch/Qt/5.7/clang_64/mkspecs/features/resources.prf:22: Unescaped backslashes are deprecated

There are two flavours of the session Id (such as 523F2857DD2B4536B7C86A479F0212E2 and 523F2857DD2B4536B7C86A479F0212E2-1:2) in the vizqlserver native API log, which means that when I use the TLV menu “Export to new tab > This session” (same for highlight), I miss lots of lines (only getting the matches for either of the two flavours but not both). I believe the session ID without the route part should be enough for identifying the session, and the two different formats should be treated as the same.

Throws this error
Could not find mkspecs for your QMAKESPEC(macx-clang-32) after trying: /anaconda/mkspecs Error processing project file: src/tableau-log-viewer.pro

when I try to run qmake -spec macx-clang CONFIG+=x86_64 -Wall /src/tableau-log-viewer.pro

I'm currently running osx 10.11.6 and anaconda 3.19.0

Is anyone else seeing something like this?

$ qmake -spec win32-msvc2013 CONFIG+=x86_64 -Wall ../src/tableau-log-viewer.pro
WARNING: H:/Qt/5.6/msvc2013_64/mkspecs/features/resources.prf:22: Unescaped backslashes are deprecated

I would like to apply AND condition on Highlight Filters would that be possible?

Scenario: I want to apply following filters on Highlight at the same time and get the results when both of those conditions are satisfied.

Filter1:

Match Field: Key
Math Type: Regex
Search Text: (begin|end)-protocol.query

Filter2:

Match Field: Value
Match Type: Contains
Search Text: query-category: Data

It is still unclear how to launch the application, can someone help me understand the same?

Using trick from: http://solutionoptimist.com/2013/12/28/awesome-github-tricks/

First image:

Users wants to see the current displayed event count.
We could make better use of status bar.

Maybe break status bar into sections so we can constantly display some relevant information?
Currently we have show what's highlighted and some search output ("found X on line Y").

Can someone pick this up?