Proactive Qlik Cloud support is more than an occasional check-in call

“Is everything still running smoothly?”

A perfectly reasonable question. But if that is the essence of proactive support, it is still mostly reactive support with a friendly veneer.

At Bitmetric, I take a different view of proactive support.

To me, it means systematically looking for signals in an environment before they develop into disruptions, tickets, or urgent requests. Not because everything is entirely predictable, but because there are often warning signs before a problem becomes an incident.

An API key that will expire soon.
An app approaching a memory limit.
A data gateway that will soon no longer be supported.

Those are things you would rather identify before they affect a user.

Proactive support is not the same as operational monitoring

Proactive support is not the same as operational monitoring.

With operational monitoring, disruptions are reported as soon as they occur. This could be a failed reload or a process that has stopped. Depending on the agreements in place, the alert goes directly to the customer, Bitmetric, or both.

Proactive support takes a broader view. It looks not only at immediate disruptions but also at risks that have not yet become incidents.

This is how the two complement each other. Operational monitoring helps you respond quickly when something breaks. Proactive support helps you identify sooner where problems may arise.

A practical example: CloudScan for Qlik

One example of how we approach this at Bitmetric is our CloudScan for Qlik: an automated daily check of Qlik Cloud tenants.

CloudScan can be purchased as a standalone service, but it is also included as standard with our Qlik Support services and when you purchase your Qlik Cloud subscriptions through Bitmetric.

CloudScan checks a tenant against more than 50 criteria, including health, capacity, reliability, security, users, configuration, and usage. We look not only at issues that require immediate attention but also at signals that indicate something may be developing.

Critical findings are reported immediately. The report also provides insight into issues that are not yet urgent but that you still need to know about.

The findings are classified, making it clear what requires immediate attention and what primarily needs to be monitored.

This prevents noise. An expired API key requires a different response than an app that is gradually approaching a memory limit. Not everything is equally urgent, but some signals are worth identifying early.

An alert is not a solution in itself

An alert is only useful when it is clear what it means, how urgent it is and what action makes sense. Sometimes immediate action is needed, sometimes it can be discussed during a regular review, and sometimes it is mainly a signal that something requires further investigation.

That is why CloudScan combines automation with the practical knowledge of consultants who work with Qlik every day. After thirteen years as a Qlik partner, and with nearly twenty years of personal experience with the platform, we know the difference between noise and a signal that genuinely deserves attention. Not every warning requires action, but every warning does require proper assessment.

What we learn from one customer also helps others

CloudScan is not a fixed checklist we created once and left unchanged.

Because we perform these checks for multiple customers, we can identify patterns. An issue we encounter while supporting one customer may also affect other Qlik Cloud environments. The same applies to what our Qlik consultants see during projects, audits, migrations and management work.

If an issue can be detected automatically and clearly poses a risk, we turn it into a new check.

That check then runs automatically for all relevant CloudScan customers.

As a result, an issue we discover at customer A today may allow us to identify the same risk at customer B tomorrow, before it becomes an incident there.

For us, this is an important part of proactive support: using knowledge not only to solve one issue, but also to recognize the same issue earlier in the future.

Proactive support in practice

Proactive support cannot prevent things from ever going wrong. A Qlik Cloud environment is constantly changing: users build new apps, data sources are modified and Qlik continues to develop the platform.

It does, however, allow you to identify risks earlier and turn experience from support and consulting into checks that are then performed automatically.

This means support is focused not only on resolving incidents, but also on keeping the environment healthy.

To me, proactive support therefore means systematically reviewing what is happening, assessing what requires attention and advising on an appropriate next step.

How healthy is your Qlik Cloud environment?

Would you like to know which anomalies and risks CloudScan finds in your Qlik Cloud environment? We can run CloudScan once at no charge on one Qlik Cloud tenant.

CloudScan is also included as standard with our Qlik Support services and when you purchase your Qlik Cloud subscriptions through Bitmetric.

We will review the key results together, after which you will receive the full report, including the details for each check.

Get your Qlik Cloud tenant checked for free with CloudScan