topic Re: Qlik Sense Enterprise Scalability Tools in Scalability

Qlik Sense Enterprise Scalability Tools

Daniel_Larsson — Fri, 30 Jan 2026 12:10:18 GMT

This tool is being deprecated, updates will be received during 2026, but thenceforth be considered deprecated.

The Qlik Sense Enterprise Scalability Tools (QSEST) are used to create and run load and performance tests towards Qlik Sense Enterprise on Windows (QSEoW).

Included parts are:

Documentation on how to use the package
Command line tool for Windows, Mac and Linux. This command line tool (gopherciser) is open source and can be found here .
GUI for Windows and Linux.

Downloadable files can be found here:
📎 Qlik Sense Enterprise Scalability Tools

Qlik Sense documents to help analyze result and log files can be found here :https://community.qlik.com/docs/DOC-15451

Change log

v1.14.1

Bugfix for entering JWT key path
Gopherciser v0.21.23 -> v0.22.2
- Avoid errors with JWT keys when running as wasm in GUI
- improved IPv6 handling
- bugfixes

v1.14.0

Added linux arm64 binaries
Removed osx binaries
Updated scheduler including support for linux arm64
Support for QSEoW Nov 2025
Gopherciser v0.20.1 -> v0.21.23
- Bugfixes
- Support nl insights objects
- Support Treedata calculation condition
- Add sn-nav-menu to supported objects.
- Add arm64 linux binaries
- Add scheduler and CPU metrics to prometheus pushed metrics
- Add configurable thinktime inbetween publishing and unpublishing sheets
- Add optional timeout settings to open app action
- Add possibility to generate empty script to template command
- Autodetect privatekey type and update default signing algorithm when using jwtsettings
- Support for PS256,PS384,PS512,ES256,ES384,ES512 and EdDSA JWT signing algorithms
- Duplicatesheet improvements
- Limit request concurrency while getting app structure

v1.13.0

Gopherciser v0.18.7 -> v0.20.1
- QSEoW Nov24 support
- Support sn-tabbed-container object
- Openapp changed for Nov24 api compliance
- New default websocket reconnect backoff pattern
- Bugfixes

v1.12.0

Updated scheduler
Gopherciser v0.18.5 - v0.18.7
- performance enhancements
- new action stepdimension

Your use of Qlik Sense Enterprise Scalability Tools will be subject to the same license agreement between you and Qlik for your Qlik Sense License. Qlik does not provide maintenance and support services for the Qlik Sense Enterprise Scalability Tools, however please check QlikCommunity for additional information on use of these products.

Re: Qlik Sense Enterprise Scalability Tools

Levi_Turner — Wed, 31 Jul 2019 20:47:28 GMT

Looks like there's a doc bug (albeit minor).

In any of the examples where you use

"claims": "{\"user\":\"{{.UserName}}}\",\"directory\":\"{{.Directory}}\"}"

This results in a user named user_#}

Like so:

Which isn't exactly pretty 😀

Swap to:

"claims": "{\"user\":\"{{.UserName}}\",\"directory\":\"{{.Directory}}\"}"

Re: Qlik Sense Enterprise Scalability Tools

Daniel_Larsson — Thu, 01 Aug 2019 07:15:59 GMT

Thank you Levi, I will make sure this is updated in the next release.

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Thu, 05 Mar 2020 22:17:02 GMT

I am trying to get the app working. It says "connection successful". But when I run it I keep getting the error "Failed to perform app selection: app<Test App> not found in artifact map".

Is there some map where I need to add this app?

Command used:

gopherciser execute -c "path to script\Script1.json"

Attaching the script1.json to this post.

Any help would be appreciated.

Re: Qlik Sense Enterprise Scalability Tools

SebastianFabian — Fri, 06 Mar 2020 08:05:42 GMT

Hi!

It's an easy fix. You just need to add an OpenHub action before your OpenApp action.

Alternatively, you can use the GUID instead of name to open the app directly.

The reason for this is the tool uses an internal "artifact map" that maps between the name of an app and a guid. When the OpenHub action occurs, the tool "sees" what apps are in the system and remembers them for future access. Then it uses this artifact map to look up the app. I attached a fixed version of your script.

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Fri, 06 Mar 2020 16:05:56 GMT

That hit the spot, right on bulls eye! It started working as soon as i added "open hub". Thank you kind sir.

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Fri, 06 Mar 2020 17:45:53 GMT

I updated the script to use generate users using a prefix, to scale to 25 users and for 25 iterations.

Created the scenario as below:

When the run the tool in command prompt, I am getting a couple of errors:

1. Sessions exceeded

2. Hub cannot be opened (presumably for hub was already open for the user from the first run) (maybe I am missing something that would allow to do "open hub" only in the first iteration and skip for the rest?

Most common error:
[90m11:26AM[0m [1m[31mERR[0m[0m failed to get DocList: EOF [36mAction=[0mopenhub [36mActionId=[0m25 [36mAppGUID=[0m [36mAppName=[0m [36mDetails=[0m [36mErrors=[0m0 [36mInfoType=[0m [36mLabel=[0m [36mObjectType=[0m [36mReceived=[0m0 [36mRequestsSent=[0m0 [36mResponseTime=[0m0 [36mSent=[0m0 [36mSession=[0m5 [36mSessionName=[0m [36mStack=[0m"EOF\nfailed to get DocList\ngithub.com/qlik-trial/gopherciser-oss/scenario.OpenHubSettings.Execute.func2\n\t/go/src/github.com/qlik-trial/gopherciser-oss/scenario/openhub.go:68\ngithub.com/qlik-trial/gopherciser-oss/session.(*PendingHandler).QueueRequest.func1\n\t/go/src/github.com/qlik-trial/gopherciser-oss/session/pendinghandler.go:88\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357" [36mThread=[0m1 [36mTick=[0m1767086597274 [36mUser=[0mQSEST_5 [36mWarnings=[0m0 [36mtimestamp=[0m2020-03-06T17:26:27.9188073Z

Any suggestions on these, please?

Re: Qlik Sense Enterprise Scalability Tools

SebastianFabian — Mon, 09 Mar 2020 10:19:16 GMT

We seem to have a bug that sometimes causes the connection test to succeed even if the header settings are invalid. After double-checking the header name and header value against the QMC settings, the issue was resolved on my end. Would you please double check:

* Virtual proxy prefix

* Header name

* Header value

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Mon, 09 Mar 2020 15:57:58 GMT

I had the previous test on November 2019 Patch 5. Now I am on February 2020.

I do not have an issue with connectivity, for it lists the apps on my test server properly. Attached is one run text file, and it has no errors.

The issue starts when it starts this in a loop for scalability testing. Below is the error when it starts iterating over 25 users over 25 runs.

ERR failed to get DocList: EOF Action=openhub ActionId=47 AppGUID= AppName= Details= Errors=0 InfoType= Label= ObjectType= Received=0 RequestsSent=0 ResponseTime=0 Sent=0 Session=16 SessionName= Stack="EOF\nfailed to get DocList\ngithub.com/qlik-trial/gopherciser-oss/scenario.OpenHubSettings.Execute.func2\n\t/go/src/github.com/qlik-trial/gopherciser-oss/scenario/openhub.go:68\ngithub.com/qlik-trial/gopherciser-oss/session.(*PendingHandler).QueueRequest.func1\n\t/go/src/github.com/qlik-trial/gopherciser-oss/session/pendinghandler.go:88\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357" Thread=2 Tick=4201200023 User=QSEST_16 Warnings=0 timestamp=2020-03-09T15:47:59.6543096Z
10:47AM ??? Action=openhub ActionId=47 AppGUID= AppName= Details=SenseEfW Errors=1 InfoType= Label= ObjectType= Received=132 RequestsSent=1 ResponseTime=0 Sent=84 Session=16 SessionName= Stack= Success=false Thread=2 Tick=4201200031 User=QSEST_16 Warnings=0 timestamp=2020-03-09T15:47:59.6543096Z

This error occurs pretty much at every run after the first.

And also the below one (was occurring in Nov 2019 P5 too).

10:50AM ??? {"jsonrpc":"2.0","method":"OnMaxParallelSessionsExceeded","params":{"severity":"fatal","timestamp":"2020-03-09T15:50:51.736728Z","message":"Access to the app is denied: MaxParallelSessionsExceeded"}} Action=openhub ActionId=497 AppGUID= AppName= Details=Received Errors=0 InfoType= Label= ObjectType= Received=0 RequestsSent=0 ResponseTime=0 Sent=0 Session=241 SessionName= Stack= Thread=15 Tick=4552568617 User=QSEST_241 Warnings=0 timestamp=2020-03-09T15:50:50.0148592Z

Re: Qlik Sense Enterprise Scalability Tools

SebastianFabian — Tue, 10 Mar 2020 09:39:55 GMT

It sounds like you're encountering some issues related to your licenses. I note that you're using a list of 3 users that are invoked multiple times in parallel. Increasing the number of users in your user list to match the number of concurrent users in the script should mitigate your problems.

Refer to the following document: Professional access allocations

The maximum number of parallel user connections for a single user of this type of access pass is five (5).If you use a license with a signed license key, accessing the QMC also counts and adds to the maximum number of parallel sessions, which is five. To avoid unnecessary session consumption, the root admin should not be allocated any type of access.

and your test may also be affected by the "cool down" timer for licensed users, which is why it fails after the first time:

When a user with the maximum number of parallel user connections ends a connection (for example, by logging out) five minutes must pass before the user can use the access pass to add another connection (for example, by logging in).

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Tue, 10 Mar 2020 15:44:33 GMT

Thank you. Since I was only doing parallel user testing, I set the iterations from 25 and 1 leaving the concurrent users at 25. This time I didn't get any max sessions used error since every user is used only once.
I am still getting the "ERR failed to get DocList: EOF Action=openhub"; not a showstopper though.

Re: Qlik Sense Enterprise Scalability Tools

Daniel_Larsson — Wed, 11 Mar 2020 15:03:01 GMT

@sri_c003 wrote:
I am still getting the "ERR failed to get DocList: EOF Action=openhub"; not a showstopper though.

This error is most likely due to authentication problems, your settings for the server etc is correct and a websocket is established, but on first command we are instantly disconnected without error. Assuming you are using header authentication? In that case make sure the headername corresponds to the header name defined in your virtual proxy.

Also please also please verify you can log in "manually" as that user towards the virtualproxy using a modify header extension in your browser. E.g. if using chrome, https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj . There are many others, same for firefox.

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Wed, 11 Mar 2020 16:00:47 GMT

Excuse me for me ignorance here, but none of the users I used show up under QMC - I felt these were virtual users with no real existence. Do all these users need to exist on Qlik and need to show up in QMC?

To add, none of these users have showed up in the tool command run output as unable to login or anything like that. I found the logs from the time when i run the tool and all entries show up as the root user --> DEV1623\qlikadmin.

Re: Qlik Sense Enterprise Scalability Tools

Daniel_Larsson — Wed, 11 Mar 2020 16:01:16 GMT

@sri_c003 wrote:

Excuse me for me ignorance here, but none of the users I used show up under QMC - I felt these were virtual users with no real existence. Do all these users need to exist on Qlik and need to show up in QMC?

To add, none of these users have showed up in the tool command run output as unable to login or anything like that.

If you can run a test without errors yes they should show up, as far as Sense knows they are real users. But as I pointed out in previous post you seem to have an authentication issue and the users are not actually let in.

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Wed, 11 Mar 2020 16:03:54 GMT

Thanks @Daniel_Larsson. I shall run the test again and check.

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Tue, 12 May 2020 16:53:47 GMT

I am able to run the tool and see the results as well as the results log. But the traffic logs are not being generated.

Help please.

Re: Qlik Sense Enterprise Scalability Tools

sri_c003 — Wed, 13 May 2020 15:11:06 GMT

Thanks @Daniel_Larsson. I got the tool working.

I am able to get the tool log file; but in spite of me telling the tool to generate traffic logs, it is not generating any tsv file.

Re: Qlik Sense Enterprise Scalability Tools

SebastianFabian — Thu, 14 May 2020 06:18:15 GMT

Hi! The tool does not generate a separate traffic log - the traffic logging is added in the regular result log. So take a look in there and you should find additional log lines marked with traffic in addition to the regular logging.

Re: Qlik Sense Enterprise Scalability Tools

Daniel_Larsson — Thu, 14 May 2020 07:24:40 GMT

In your screenshot you have clearly named the file *.log so in your case you would have a file called .log in the path you defined. This is a .tsv file, if you want it to work in the analyzer you need to save it with .tsv extension.

Re: Qlik Sense Enterprise Scalability Tools

Daniel_Larsson — Thu, 14 May 2020 07:28:53 GMT

And just to note, We normally do not recommend having full traffic turned on if you want to analyze performance as this would create a very big result file, and you would most likely performance test your harddrive instead. For performance analysis using the analyzer no traffic is needed. If you want for some reason to see the response time of individual requests you can turn on the traffic metrics instead of traffic. The only reason to turn on traffic would be to see all sent and received requests including everything in the result file, i.e. mostly for debugging.