Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
QSSTAnalyzer.zip
This package contains a Qlik Sense app, which can be used for analyzing Qlik Sense performance test results generated by the Qlik Sense Scalability Tools and the Qlik Sense Enterprise Scalability Tools.
Included parts:
SCResultAnalyzer.zip
This package (referred to as SC Results Analyzer) contains a set of QlikView documents, which can be used for analyzing both QlikView and Qlik Sense performance test results generated by the Qlik Sense Scalability Tools and the QV Scalability Tools.
Included parts:
------------------------------------------------------------------------------------------------------------------------------------------
Update 2021-01-04:
Update 2020-12-18:
Update 2019-11-14:
Update 2019-10-31:
Update 2019-10-14:
Update 2019-05-17:
Update 2017-09-26:
Update 2017-03-17:
Your use of Scalability Tools will be subject to the same license agreement between you and Qlik. Qlik does not provide maintenance or support services for the SC Result Analyzer and QSSTAnalyzer, however please check Qlik community for additional information on its use.
Thanks Sebastian for the reply, let me check on these couple of points and get back to you.
Thanks Sebastian , its working now
Hi All,
I wanted to see if anyone else came across the issue of some fields missing from the QSST server logs which are causing QSSTAnalyzer.qvf reload to fail? We were previously using QSST 5.1.0 and QSSTAnalyzer.qvf from a year ago, but seems like to setup process changed significantly over the year.
In order to make this app (QSSTAnalyzer.qvf) to reload succesfully, we had to make some changes into __SUB LoadGopherciser script:
- Time rather than time
- Level rather than level
- Error rather than Errors
- missing Warnings field
- missing Success field
and couple of other changes similar to the above.
Question is - are we using the correct fields to feed into this or we are missing a step of this setup?
We are using QSST 5.6.0 and files used for QSSTAnalyzer.qvf are the results of user defined collector set, stored directly on the nodes of the cluster we were hoping the scale our app against.
Are we missing some steps of the setup? Any advice will be highly appreciated and thanks in advance for any help!
kind regards,
Michalina
Are you using the full folder structure?
Are the logs placed in the correct folder?
I suspect that you have placed the files in the Gopherciser-folder.
The Qlik Sense Scalability Tools result logs should be placed in the Exerciser-folder.
Yes, the field naming is inconsistent and that's why there are more than one folder for results.
Un-zip the FolderTemplate.zip and place the result files, ending with _scenario.txt, in the Exerciser folder instead.
/lars
Hi Lars,
Thanks a lot for your response - this really helped! We can now see the correct population in all of the charts.
kind regards,
Michalina
Is the QSSTAnalyzer compatible with Qlik Sense June 2018 ?
The tools does not create or collect the Windows Performance Counters automatically. This has to be setup and handled manually.
See the documentation for the Qlik Sense Scalability Tools https://community.qlik.com/t5/Qlik-Scalability/Qlik-Sense-Scalability-Tools/gpm-p/1490846 for a recommended handling.
The csv-files created by the Window Performance Counters should then be placed in the ServerLogs folder in the folder-template. It is often a good idea to restart the Performance Counters between executions so there is one Performance Counter csv-file per performed execution.
Depending on what app you use to analyze the results you might have to secure some things. Machines, load client and server/servers should have synchronized clocks and time zones. Some of the analysis applications also depend on machine name in combination with the timestamp to connect a test with resource consumption.
Good luck with you analysis!
/lars