The step from 4.x to 5.0 indicates this is a major release.
Very much so in fact. The main focus of the new version is on reload alerts. Rich email alerts were introduced in Butler 4.2, but that was really just the testing ground for what’s now available in 5.0.
Here’s the short version of what’s new:
Alerts for failed or aborted reloads can be sent to Slack, MS Teams, outgoing webhooks, MQTT or as email.
Alerts sent as email, Slack and MS Teams can all make use of all the rich formatting and layout options available on those platforms.
Alert emails can be sent to the owner of the Sense app that failed reloading.
A new API for doing partial (and full) app reloads was added. This means it’s now possible and even easy to do partial app reloads in Qlik Sense. One of the epic QlikView features finally become usable in Qlik Sense!
Curious what the alerts look like in reality? Check out this video for a hands-on demo:
What’s Traefik and how does it relate to Qlik Sense?
Traefik is one of today’s most hyped reverse proxies. It’s available in both a commercial and a (very capable!) open source version. According to the company behind Traefik it’s been downloaded more than 2 billion times – that’s a lot…
In this blog post we’ll take a look at how Traefik can run natively on Windows server, providing services to a Qlik Sense Enterprise on Windows cluster. We will see how this can make Qlik Sense easier to use for end users as well as easier to run and operate for sysadmins.
Specifically, we’ll use Traefik to set up TLS secured access (a.k.a. https) to Qlik Sense, while at the same time establishing a solid platform to which we can add more features in coming blog posts.
Starting with the basics makes sense though – let’s get to it!
Qlik Sense is very much my go-to tool for many data related questions. It’s very powerful to be able to throw together a proof of concept or test a hypothesis in half an hour. Seeing is however believing, so those prototypes does need some polishing before they can be seen as production grade.
I have always pushed my peers in the Qlikosphere to become better at using icons for their Qlik Sense apps in general, and also for the sheets within those apps. Having an icon for a sheet within an app makes it way easier for the user to find a particular sheet – humans are visual by nature.
The basics are the same, i.e. one-click creation of Qlik Sense apps, using regular Sense apps as templates. Several new features however take the tool to a new level, making it easier to set up, manage and more enterprise grade. Good news thus!
Docker is one of those tools that have the potential to fundamentally transform how you develop and run software – once you have tried Docker it is hard to imagine going back to something else.
In previous posts we have seen how Butler, Butler SOS and Butler CW can be run as Docker containers.
But we can do even better – why not control all the Butler tools from a single docker-compose file? Maybe even specifying the dependencies on influxdb and mqtt in there too?
Setting this up is incredibly easy – a single docker-compose file tells Docker what containers to use, and some config files tells the Butler tools where to find things.
Following up on previous posts (here and here) about the Butler family of tools being Dockerized, here is another one on the same topic:
Butler SOS can now be run in a Docker container.
This is good news as it makes it a lot easier to set up real-time monitoring of a Qlik Sense enterprise environment, compared to the previous (still working, btw) method of installing Node.js and then running Butler SOS on top of Node.