Suggest an Idea

[Ricardo_Gerhard]

Currently, when a problem happens with a task, we need to access the QMC and understand the issue. We must to be proactive and alert the users this issues.

I guess that a pop-up on qmc and mail alert integrated into QMC will be very helpfull.

[dwforest]

Especially mail notification.

Currently have added mail on errors as described in the Help that adds the SMTPAppender to the logs, but it would be nice to have this integrated to the QMC and more control over the message.

[Ricardo_Gerhard]

Yes David,

The same resource that has Qlikview, but we could create some improvements as:

- Notification message;

- Create a link between QMC and e-mail;

[mountaindude]

Yup, better notifications would certainly be useful.

I solved it by adding a small microservice (a.k.a. Butler) that listens to the log messages via the Log4Net framework, and then forward those events (failed tasks, users logging in/out, ... anything that ends up in the log files can also be captured and acted on in the microservice).

My personal notification favourite is sending messages to Slack channels. One channel for failed reloads, one for user sessions abruptly terminated, one for security violations. Works a treat.
The tool is open source at https://github.com/ptarmiganlabs

[Ricardo_Gerhard]

Sure Goran, it´s very useful. Thanks for sharing.

I think that this features should be included in the main product. The companies should be able to keep the environment working fine.

[Michael_Tarallo]

I'm pleased to say - this is also been added to the system, there are a number of ways to achieve this now, but making it part of the product would be ideal. I have up voted the on in our system - however I don't see support for this just yet - as it was only opened a few weeks ago. I submitted my request as well.

[tim_ringle]

As a newcomer in the Qlik Sense Admin space, this is would be VERY helpful. 

[tim_ringle]

We got around this by having a separate monitoring tool look at the QVD dates and email us when the last modified date is more then 24 hours old. It is a poor solution but at least it is something. We don't what reload task failed or why but at least in most cases we are looking at the refresh problem when the calls start to roll in.  

[Steven_Haught]

This would be incredibly helpful. Especially to any new admin. Nprinting can do this if you set it up in the settings and point directly to the task/task log that failed. Would be good to have that same functionality in QS. 

[Tami]

This is extremely important during the reloads. There are options outside of the QMC such as alerting and setting up SMTP notifcations but this should be simple for the organization as it is in QlikView. Notification of reload errors are crucial for us to keep the applications reliable. Our users become disengaged if they cannot rely on the data to refresh frequently.