Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
ne_kau
Contributor III
Contributor III

Qlik alert to notify if hub and qmc are not accessible

Hi,

Is it feasible in Qliksense to generate alerts using Qlik Alerting or Qlik cli for getting notifications if hub and QMC are not accessible or unable to open?

Regards,

Neha

Qlik Alerting  Qlik Cloud 

Labels (3)
2 Replies
Lisa_Sun
Support
Support

Qlik Alerting has two alerts.  System Alert creates the notification based on the task reload status and data alert.  But Data Alert can be used for the alert based on the data value.  So you can send the alert based on the error in the proxy or repository logs. 

 

https://help.qlik.com/en-US/alerting/May2021/Content/QlikAlerting/data-alerts.htm

 

But when Hub and QMC do not work correctly, the cause can be vary. So it is hard to create the right alert on it.  The best way is to keep monitoring our monitoring apps: operation monitor and log monitor.  Filter it by error.  

 

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!
mountaindude
Partner Ambassador
Partner Ambassador

"...getting notifications if hub and QMC are not accessible or unable to open?"


Indeed, your question can be interpreted in different ways. 

One way to view it is to check in the various Sense logs for warnings and errors, then alert when that happens.
But things may look fine in the logs, but Qlik Sense's internal web server is not working, or some external firewall (outside the scope of Qlik Sense) is incorrectly configured and preventing  access to the hub, etc.
If you want real-time monitoring of this you'd first need to get the log events out of Sense, then alert on them.
There are various ways of doing this, my personal go-to solution is Butler SOS.
It let's you forward log events from Sense to Butler SOS, where you can then act on them, visualise them in Grafana, create alerts etc. Butler SOS is open source and thus free to use.
I am slightly biased though as I am also the creator of that tool.. But it's pretty solid and used all around the world.

The other option is then to use a tool that essentially pretends to be an end user logging in and using some part of Sense. The tool takes screen shots along the way and compare those with previously recorded reference screen shots. If things look different that indicate something is not working the way it's intended.
This solution is gold as it gives you insight into what your Sense environment *really* feel like for your end users. 
You might have a huge Sense server capable of many users and big apps, but a slow network connection to Internet. The end result is still a poor end user experience - and this kind of monitoring capture that. 
As for tools this options requires a bit more development, configuration etc. Tools like Selenium etc are very powerful but also demanding when it comes to setting up, configuring and running. 

Please mark the post as a solution if it provided you with a solution to the topic at hand. Thanks!