Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The Qlik Alerting September 2020 release includes a new Qlik Sense monitoring app that will allow you to better understand what is happening with your Qlik Alerting environment. This will enable you to see the load on the system, the average processing times, the reason why an alert may not have been sent to the recipient and other information.
We have added a few shortcuts for you to get the data connections setup appropriately. Please follow the steps below to get the monitoring app setup:
Setting up the Data Connectors in Qlik Sense.
This is a little detailed to setup manually so we have added a .bat file in the installer to push the connections using the correct attributes from your Qlik Alerting installation. You need to have completed the registration process if this is a new install of Qlik Alerting as this process will use the data source and Qlik Alerting config settings to create the data connectors.
Steps to follow:
Import and reload the Qlik Alerting Monitoring Qlik Sense application
Once the connections have been created you can now import the Qlik Sense application that can be found in the C:\Program Files\Qlik Alerting\setup\monitoring-connection folder.
Steps to follow:
Troubleshooting
If the reload does not work straight away here are a few things to check:
Optional: Steps to create the data connections manually
If you really cannot follow the simple steps above to create the data connections, for security reasons for example, you can follow the instructions below to create them manually.
Setup the monitor_alerting_login data connection
This request makes the authentication request to Qlik Alerting and is required to get the authenticated session token to run the monitor_alerting api connections to actually retrieve the data.
Enter the URL updating your <QA_Server> and <QA_https_port> values
https://<QA_Server>:<QA_https_port>/api/login
In the body section that appears enter the following details adding your user and password as you would use to login to the Qlik Alerting portal
{"user":"<your_QA_username>","password":"<your_QA_password>"}
In the query headers section enter
Name | Value |
content-type | application/json |
You are now setup to use this API to create a request to authenticate against Qlik Alerting. Follow the monitor_alerting setup below to see how this works.
Setup the monitor_alerting data connection
This request will be used to retrieve data from Qlik Alerting. We will be passing a different endpoint URL through this connection in the monitoring app script so we do not need to create a connection for each endpoint.
NOTE: this process is a little more complex as we will need the session token from running the monitor_alerting_login result to actually run this process. This is covered in the steps to help you through this.
edit the <QA_Server> and <QA_https_port> in the Let vURL variable
LIB CONNECT TO 'monitor_alerting_Login'; Let vURL = 'https://<QA_Server>:<QA_https_port>/api/login'; Connection: LOAD [token], [userId], [userName], [firstName], [isAdmin], [license], [expiresOn] ; SELECT "token", "userId", "userName", "firstName", "isAdmin", "license", "expiresOn" FROM JSON (wrap on) "root" WITH CONNECTION( Url "$(vURL)" ) ; // Set new variable values LET vAuth = Peek('token',0, 'Connection'); LET vUserId = Peek('userId',0,'Connection'); LET vUserName = Peek('userName',0,'Connection'); LET vAdmin = Peek('isAdmin',0,'Connection'); Trace >>>; Trace >>> Auth $(vAuth); Trace >>> User $(vUserId); Trace >>>; drop table Connection;
https://<QA_Server>:<QA_https_port>/api/groups/users
In the query headers section enter the following two
Name | Value |
authorization | <auth value copied from step 3> |
userid | <user value copied from step 3> |
You have now setup the two data connections and should be able to import and reload the Qlik Alerting Monitoring.qvf application as per the instructions above.
You can also find a copy of the QVF that was released with the September 2020 version attached to this document.
Hi ,
I follow your instructions for create manully monitor_alert_login Connection but I have this error:
"The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."
Could you help me ?
@steeramp First question i would have is whether you have the port correct as your screenshot says 4452 rather than 4552.
Secondly if you're getting an SSL error then there are some TLS settings in the C:/qlik alerting/gateway/config/default.json file... If you are using TLS 1.2 or 1.1. you will need to enable these as by default QA will use the latest (TLS 1.3).
Let me know if that helps.
I follow you one screenshot about my Defaul.json file: what I need to modify in your opinion?
.. and about the port , I'm a little confused , of course is 4552
@steeramp Re the port being different in the gateway config file. The key point to remember is that the value in the c:/program files/qlik alerting/config/default.json will override the value in the config files for the specific services. So your 4452 value in that file allows you to access with port 4452 rather than 4552.
I can replicate your error when Qlik Sense is using an SSL connection (i.e. trusted certs) but Qlik Alerting is not. I think this is likely your issue here and you could revert to http to test. See the help site link for info on how to add your SSL certs.
Hi ,
I follow your instructions for create manully monitor_alert_login Connection but I have this error:
"The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."
I checked also the default.json file in c:/program files/qlik alerting/config
I followed also the instruction about certificates, I copied the same certificates I created in qlik sense to connect qlik alerting
do you have any hint to solve this problem?
it is necessary to select in Certificaton Validation: Skip Server Certificate Validation