Note: Our legacy performance testing offering can be found here: Qlik Sense Scalability Tools.
The Qlik Sense Enterprise Scalability Tools are used to create and run load and performance tests towards Qlik Sense Enterprise for Windows (QSEfW) and Qlik Sense Enterprise on Kubernetes (QSEoK) deployments.
Included parts are:
Qlik Sense documents to help analyze result and log files can be found here :https://community.qlik.com/docs/DOC-15451
v1.5.0 - v1.6.0
v1.4.0 - v1.5.0
v1.2.0 - v1.3.0
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.
I have probably a stupid question, sorry if it is the case.
I don't get why there are 2 concurrent Scalability tools.
If the purpose is to use it on a windows environement, when should we prefer Qlik Sense Enterprise Scalability Tools vs Qlik Sense Scalability Tools ?
I have seen that we can only conduct performance tests with Qlik Sense Enterprise Scalability Tools, so I also want to pre-cache some apps, I will install Qlik Sense Scalability Tools. But for load performance tests, which one should I prefer ?
Dear Scalability Tool Experts,
I am trying to run this tool on On-Premise QSEoK deployment. I am getting following error when testing connection. Error code in renderer.log is Exit Code 137. Please check and provide some input.
Version: v0.5.5 Failed to connect using 2 connection test functions. Error #1: failed to connect to engine over web socket: Failed connecting to sense server: Error connecting to Sense: unexpected HTTP response status: 401 Error #2: failed response code: 401 Unauthorized
I have followed the instructions given in random-qseok.html
Generating the SSH key pair on Master Kubernetes Node
Configuring the QSEoK deployment by enabling JWT authentication on QSEoK with public key created above
Ensure there are adequate license for virtual Users in Console >> Licenses
Importing and publishing the test apps
Modifying the sample test script
Modify the following fields to match the QSEoK setup configured above:
connectionSettings.server: The hostname of the QSEoK deployment.
connectionSettings.jwtsettings.keypath: The path to the private key (mock.pem in this example as the key is stored in the same folder as Gopherciser).
connectionSettings.jwtsettings.jwtheader: The JWT headers as an escaped JSON string.
connectionSettings.jwtsettings.claims: The JWT claims as an escaped JSON string.
loginSettings.settings.directory: The name of the user directory.
scenario.action: OpenApp.settings.appguid: The GUID of the test app.
Error message while executing command gopherciser.exe execute -c qseok.json
2020-09-05T07:23:41-05:00 Err<0> Warn<0> ActvSess<0> TotSess<0> Actns<0> Reqs<0>
2020-09-05T07:23:51-05:00 Err<6> Warn<6> ActvSess<4> TotSess<10> Actns<10> Reqs<74>
TotErrors<10> TotWarnings<10> TotActions<10> TotRequests<90> Duration<13.4330929s>
10 errors occurred:
First error: 8 errors occurred:
* Unexpected status code: 401 (GET https://hostname:port/api/v1/collections/favorites): unexpected response status code<401> expected<>
* Unexpected status code: 401 (GET https://hostname:port/api/v1/quotas?reportUsage=true): unexpected response status code<401> expected<>
* Unexpected status code: 401 (GET https://hostname:port/api/v1/locale): unexpected response status code<401> expected<>
* Unexpected status code: 401 (GET https://hostname:port/api/v1/users/me): unexpected response status code<401> expected<>
* Unexpected status code: 401 (GET https://hostname:port/api/v1/features): unexpected response status code<401> expected<>
* Unexpected status code: 401 (GET https://hostname:port/api/v1/spaces?limit=100): unexpected response status code<401> expected<>
* failed to get spaces <<html>
<head><title>401 Authorization Required</title></head>
<center><h1>401 Authorization Required</h1></center>
>: unexpected response status code<401> expected<>
* Unexpected status code: 401 (GET https://hostname:port/api/v1/licenses/status): unexpected response status code<401> expected<>
By reading this thread I see that running the tool uses actual users and consumes actual licenses.
So if we would like to test our environment we need to set up a Test copy of our Prod environment.
Could we then use our Prod license in the Test environment also or do we need to ask for a specific Test license?
(We are on the Signed license model if that has any importance)
It is a valid question, and I’m sure this isn’t clear to everyone. Qlik Sense Enterprise Scalability Tool (QSEST) is our latest offering and this is where our tool development work mainly is happening, hence this is the tool for the future. A main difference and advantage that comes with QSEST is that it can run from Windows, Mac or Linux whilst Qlik Sense Scalability Tool (QSST) is windows only. If you are new with the tools I suggest you go for QSEST. The only key functionality that exist in QSST which is not yet supported for the QSEST is the regression capability.
Is there any prepared Sense app to anlyze the logs? Also any way to setup schedules to run test? i.e. check differnces in performance during the day
The QSSTAnalyzer Sense app is compatible with Gopherciser/QSEST text executions, see the following topic: https://community.qlik.com/t5/Scalability/Scalability-Results-Analyzer/td-p/1493648
There is no built-in scheduler but gopherciser (the underlying test tool) is fully operational as a command-line tool so it can be scripted with cron, bash, the Windows scheduler or any number of other solutions. See the documentation for Gopherciser, included with the QSEST package.
Thanks for reply.
Found earlier how to schedule so that is up (https://github.com/qlik-oss/gopherciser/blob/master/docs/availability-testing.md)
Also had a look at QSSTAnalyzer, but since I only have the .tsv files that didnt look like good option.. Will have to built something myself then
We are trying to use this tool to do performance testing with QlikSense hosted on Google Cloud Environment where authentication is SAML. Can we use scalability too to connect with QlikSense on GCP?