Tableau is undergoing maintenance for our licensing service

Tableau is undergoing maintenance for our licensing service on Saturday, April 11, 2020 from 8:00AM – 10:00 AM PT (3PM – 5PM UTC). During this time, Desktop and Server product activation and registrations will be unavailable. Please wait for maintenance to complete before activating your products.

source https://community.tableau.com/

Coronavirus (COVID-19) NON Reporters

Everybody’s favourite subject again… the coronavirus. This time I was having a conversation in the office about the number of cases next to countries. This was interesting, especially with countries such as Turkey (which was the focus of our conversation) who have not reported a single case as yet.

Because of this I looked at the probability/risk of an infectious disease outbreak based on a few factors:

  • Reported – Has the country reported a case?
  • Population – How many people are in the country? A greater population means it can be harder to control an outbreak.
  • Population Density – Is the country densely populated? Greater density can increase community transmissions.
  • Tourism – Is there a lot of international traffic? Country to country infection is generally caused by tourist activity. Revenue through tourism is an indicator of traffic.
  • Healthcare – Is there good investment in healthcare? Healthcare investment can indicate a country’s ability to deal with an outbreak.

This of course doesn’t account for proximity of other infected countries, but is an interesting start. You can see proximity using the map however.

So what did it tell me about Turkey?

It told me that Turkey actually seems to be at a high risk. With a high tourist income, a large population (with a not too insignificant density) and a fairly low healthcare investment compared to other countries of a similar size along with the proximity to other infected countries Turkey would not be the top of my holiday list at the moment.

You can see the viz for this here: https://public.tableau.com/profile/jake3777#!/vizhome/NovelCoronavirusCOVID-19/Non-Reporters 

This data came primarily from the World Health Organisation and Knoema.

Upgrading to 2018.x and changes to ‘K’ Analysis – Pt1

So you have upgraded to 2018.x and you’re wondering if your existing log analysis will continue to work. The good news is it will. The log locations are within the same directories so if you’re using Splunk there should be no changes necessary on your forwarder and the original log entries you will be indexing exist too, so your favourite dashboards will still work also.

So what’s new?

In 2018.x there is a whole load more in terms of logging and it opens up a lot more potential for the conscientious admin.

I will be doing a small series on what’s changed what we can do now and what to watch out for over the coming weeks, but I wanted to start off with an update to the ‘K’ analysis.

You will be happy to hear there is loads more available to us in the ‘K’ analysis log entries for VizQL and although I am still in the process of documenting it all, I wanted to share entries you can look for in your logs that I am currently looking at. You will notice that the log entries are a lot more granular which means you can see the step by step what’s going on rather than; its starting, it’s ended, here is the query and here is the summary. I hope that this will provide detailed execution plans so we can see when data sources become of a particular size and go off a cliff due to interesting and fantastical processes, but that remains to be seen. What it will show us is parsing and evaluations which is immediately useful to the developer when troubleshooting.

so without further ado…

‘K’ Analysis Entries (so far):

activity-and-resource-tracing-set-offs
appoption-override
begin-abstract-query
begin-bootstrap-cache-load
begin-bootstrap-session
begin-bootstrap-session-connect-data-sources
begin-clone-and-recreate
begin-command-for-sess
begin-command-for-sess-int
begin-compute-quick-filter-state
begin-compute-x-axis-descriptor
begin-compute-x-set-interp
begin-compute-y-axis-descriptor
begin-compute-y-set-interp
begin-create-protocol
begin-create-session
begin-data-interpreter
begin-densification-interpreter
begin-execute_query_evaluate_join
begin-filter-categorical-domain
begin-generating-checksum-of-file
begin-load-wb
begin-localcalc-interp
begin-parse-datasource
begin-parse-datasources
begin-parse-dom
begin-parse-local-data
begin-parse-shared-view
begin-parse-windows
begin-parse-workbook
begin-parse-worksheets
begin-partition-data
begin-partition-interpreter
begin-prepare-mapping-tables
begin-prepare-primary-mapping-table
begin-prepare-quick-filter-queries
begin-qp-create-tables
begin-qp-federate
begin-qp-federated-evaluator
begin-qp-format
begin-qp-optimize
begin-qp-resolve
begin-qp-rewrite
begin-qp-run-query
begin-query
begin-request
begin-secondarydsinterpreter-apply
begin-sess-load-workbook-dom
begin-sort-panes
begin-sql-temp-table-tuples-create
begin-update-sheet
begin-upgrade-workbook-dom
begin-visual-model-producer
begin-wimage-complete-vmodel
begin-wimage-compute-layout
begin-wimage-compute-vmodel
begin-wimage-render-bitmap
begin-world-update
binding-info
bookmark-location
cache-purge
cachingdomparser-getdom-stats
cancel-request-end
cancel-request-received
child-process-created
cli-configure-finish
close-log
command-post
command-pre
compilation-cpu-features
compute-percentages
compute-task-error
connection-closed
connection-close-request
connection-communication-failure
connection-communication-warning
connection-info
connection-info-mismatch
connection-startup-begin
connection-startup-end
connect-using-keychain
construct-protocol
construct-protocol-group
cpu-info
crash-reporting
create-client-connection
create-resultset-accessor
database-error
database-registry-shutdown-begin
database-registry-shutdown-end
data-inserter-summary
data-server-session-statistics
data-server-table-statistics
data-server-temp-table
datasources-location
dbregistry-construct
dbregistry-create
dbregistry-load
dbregistry-release
dbregistry-unload-finish
dbregistry-unload-prepare
destroy-session
destruct-protocol
destruct-protocol-elapsed
destruct-protocol-group
destruct-protocol-without-context
dll-version-info
ds-connect
ds-connect-data-connection
ds-lazy-connect
ds-lazy-connect-data-connection
ds-lazy-load-metadata
ds-load-metadata
ds-parser-connect
ds-parser-connect-extract
ds-validate
ds-validate-extract
ec-drop
ec-load
ec-store
empty-query
end-abstract-query
end-bootstrap-cache-load
end-bootstrap-session
end-bootstrap-session-connect-data-sources
end-clone-and-recreate
end-command-for-sess
end-command-for-sess-int
end-compute-quick-filter-state
end-compute-x-axis-descriptor
end-compute-x-set-interp
end-compute-y-axis-descriptor
end-compute-y-set-interp
end-create-protocol
end-create-session
end-data-interpreter
end-densification-interpreter
end-ds-connect
end-ds-connect-data-connection
end-ds-lazy-connect
end-ds-lazy-connect-data-connection
end-ds-lazy-load-metadata
end-ds-load-metadata
end-ds-parser-connect
end-ds-parser-connect-extract
end-ds-validate
end-ds-validate-extract
end-execute_query_evaluate_join
end-filter-categorical-domain
end-generating-checksum-of-file
end-load-wb
end-localcalc-interp
end-parse-datasource
end-parse-datasources
end-parse-dom
end-parse-local-data
end-parse-shared-view
end-parse-windows
end-parse-workbook
end-parse-worksheets
end-partition-data
end-partition-interpreter
end-prepare-mapping-tables
end-prepare-primary-mapping-table
end-prepare-quick-filter-queries
end-qp-create-tables
end-qp-federate
end-qp-federated-evaluator
end-qp-format
end-qp-optimize
end-qp-resolve
end-qp-rewrite
end-qp-run-query
end-query
end-request
end-secondarydsinterpreter-apply
end-sess-load-workbook-dom
end-sort-panes
end-sql-temp-table-tuples-create
end-update-sheet
end-upgrade-workbook-dom
end-visual-model-producer
end-wimage-complete-vmodel
end-wimage-compute-layout
end-wimage-compute-vmodel
end-wimage-render-bitmap
end-world-update
environment
eqc-log-cache-key
eqc-store
ewac-load
ewac-store
excp
extract-archive-file
extract-archive-files
fault-reporting-init
federation-database-pool-cleanup
geosearch-cache-load
get-cached-query
getdom
global-infrastructure-shutdown
hyper-connection-string
hyper-libpq-protocol
init-maindb-begin
init-maindb-end
license-check-end
license-check-sleep
license-check-start
listen-tcp
localdata-location
locale-info
lock-session
log-auth
log-close
logging-end
log-keychain
log-rotate
mapsources-location
memory-info
memory-usage
msg
odbc-protocol-read-primary-keys
odbc-protocol-read-statistics
open-log
operating-system-info
pack-response-cache-key
parse-dashboard
parse-dashboards
parse-window
parse-workbook-attributes
parse-worksheet
PathAccessChecker
previous-log
protocol-added-to-group
protocol-cache-lifetime-in-minutes
protocol-cache-size
protocol-logsession
protocol-removed-from-group
qp-batch-summary
qp-cse
qp-info
qp-optimize-dependencies
qp-optimize-fusions
qp-query-begin
qp-query-end
qp-query-fusion
query-begin
query-end
query-plan
query-result-sent
query-running
read-foreign-keys
read-metadata
redis-pubsub
redo-log-not-persisted
repository-location
request-header-received
resolve-preferred-import-binding
resource-limits
rotate-log
RuntimeTelemetry
scheduler-startup
server-ready
server-startup-options
server-telemetry
serviceRegistrationId
service-start
session-close-stats
session-modified-at-cmd-start
session-type
shutdown
sqlcolumns
sqltables
srm-internal
startup-info
stop-sweeper
subquery
supp-clone-and-recreate
supp-load-wb
tcp-ip-client-allowed
tile-cache-fill
unlock-session
vmp-generate-axis-encodings
VqlSessionClear
vqlsession-getxmlfiledom-try-cache
windows-timer-resolution
workbooks-location
zlib-compress-data
zlib-uncompress-data

This list will be updated as soon as I have finished my migration projects at work but should be fairly comprehensive already.

TC18

Hi All,

Apologies, I know it has been a significant time between posts but the last year has been super busy with Windows OS issues on my servers which has absorbed a good deal of time.

I wanted to start off with a feel-good post, so… TC18 happened. In New Orleans and it was amazing! Bigger and bolder than ever before, this was the mother of all conferences.

 

NOLA

Braindates

For me this conference was by far the most influential as I took to the newest conference feature – Braindates.

Braindates is a concept where you fill out your bio in the TC app and then add a conversation topic. Anybody could then book some of your free slots and you would meet with them in the Braindates area for a chat.

For me, my topic was (with no surprise) “Monitoring and Log Analysis” and it proved extremely popular with other attendees. In fact it was so popular that I had to change some of my sessions to group sessions and I am having to arrange to meet people after the conference via a Webbex or Lync to catch up with all of those I was not able to meet.

Braindates

In total I met with people 26 times, topping the Braindates leader-board and ended with me being given a card by the Braindate team for my efforts… which was a really nice touch!

BraindateCard.png

Sessions

The Sessions were great and with 658 speakers there was no lack of content! I followed the Server Admin track and especially enjoyed learning about kerberos powered row level security.

This year also, sessions have been made available on YouTube. This is a great way to keep up to date and is definitely worth a watch! Tableau YouTube

I will be going through the sessions to catch up on anything I missed out on.

Data Night Out

The Data Night Out was as awesome as usual with a great venue. If you weren’t there, it was at the New Orleans Super Dome, an amazing structure in itself, it was filled to the brim with interesting events, food and drinks.

TC18DNO2IMG_2414IMG_2429

Twitter

A blow-by-blow of the event is available on my twitter feed and can also be found using the hashtag #TC18

On a final note, I have now opened up my twitter account to allow DMs from all people, so if you have a question, feel free to message me directly.

Tableau Conference – Data 17

Hi all,

Apologies this is late, but I stayed out in Las Vegas a little longer than expected. I believe I was one of the last to leave!

So Data 17 happened – and it was in Las Vegas. To give you an idea of scale, I averaged 17,012 steps a day with a maximum of 27,773 on the Wednesday > Thursday with the Data Night Out.

So first things first, before you step foot inside, you will have had the Data17 app. This unsung hero was your guide to everything you needed to know and more. Without this bit of kit, you would have easily missed a cool session or missed out on something happening in the Data Village.

If you ever join a Tableau conference, you will need this as your conference bible.

It also works as a great tool for talking to people. Let people know where you are or where to meet and grab a beer.

SESSIONS

The sessions this year covered a great array of subjects with some brilliant speakers. Hopefully you managed to catch the talk by Paul Banoub who covered our service at UBS.

I steered towards the technical and server admin track for obvious reasons but started my week with a meet-up and an intro to the conference to try and get the best out of my week.

This was an opportunity to talk to like-industry professionals and was where I met members of my user community from around the world, which without I would not necessarily have an opportunity to meet fact to face.

This session helped me help myself. With a review of the week, you were able to ask questions that you were a little too embarrassed to ask otherwise, like “where is…” or “what do I need to do to…”. If you are a conference newbie or seasoned, this should be something you see and was a great decision for me.

Everything you need to know about what is coming out soon in Tableau and wow, there are some great things on their way.

Tableau on Linux. It is the big thing in the Tableau world at the moment and due to my hectic daily schedule, I haven’t managed to give this much attention, however the conference was my chance to catch up. So what were my thoughts? I thought it looked interesting, but in this introduction session to it, it seemed to have a few minor issues which I hope will be ironed out with time. Offering Tableau on a free OS is a big step forward and will open up avenues for web developers who solely rely on Linux.

Always a great opportunity to see if what you

are doing is considered best practice.

Devs on Stage served up more goodies with new upcoming features.

These two were great. Their insight into data and how they have used it within their career together.

Back on the Linux track, this session showed the detail of what Tableau on Linux was like under the covers. The most interesting thing was that all of the extra features available to Tableau on Linux, such as the hot configuration change will ALL be available on Windows.

Keeping up to scratch with my security knowledge. If you haven’t seen my post on Kerberos, feel free to check it out.

High availability is the holy grail for server admins. Making sure you have minimal downtime, especially when Tableau is tied into operations or revenue streams.

Here are some new tools, which although are not quite ready for our environment due to some limitations, are definitely worth keeping an eye on. All are available on GitHub.

My favourite, by far. Adam Savage is a bit of a hero for me. I especially enjoyed his keynote. Well done Tableau for booking him.

NETWORKING

The biggest thing, apart from the great sessions, inspiring keynotes and the epic Data Night Out, is the people you meet. You will meet the absolute leaders and superstars in this industry and you will find out that they are just as interested in your story as you are of theirs. I met a number of great people and look forward to keeping contact with them.

The UBS team. Paul and I managed to meet some of our users from the US. It was a great opportunity to talk to them face to face and will help build on our working relationships within the firm. There was an incident with James and I with a see-saw at one point. I have the video, but you have to be kidding if you think I am going to share it on here!

DATA NIGHT OUT

This was the party of the year. It was absolutely amazing and allowed everyone to let their hair down and socialise. Thanks Tableau. Was brilliant.

NEXT YEAR

Next year is in New Orleans. Not 100% sure I can make it, but will definitely try!

VEGAS STRONG

I didn’t want to finish this post without acknowledging the Mandalay shooting. This was a terrible incident which was located where the conference was based. Because of this, over $126,000 was raised at the conference for the victims. This is a great contribution towards this very worthy cause. #vegasstrong