Setup: Having a Checkmk Raw installation locally. And a (so far temporary) Checkmk Cloud instance. I would like to connect the two, so that monitoring items from Cloud appear in the internal Checkmk. I don’t see a way to do that, am I overlooking something?
No, you are not overlooking something. Checkmk Cloud only talks to Checkmk Cloud in distributed monitoring setups. These are limitations that my employer enforces. The reasons are that enterprise features should be either paid for or used solely from Open Source editions.
I do not always agree on such enforcements, but do understand them. You might use Cloud - Cloud (which just works for 30 days, or when paying) or Raw - Raw (which always will work and even Cloud to Raw downgrades are possible).
Thanks, but how about Checkmk Enterprise using Checkmk Cloud, then? I.e. in my example, I use an Checkmk Enterprise on-prem.
@troelsarvin you are talking about Checkmk Cloud as in “the SaaS offering”, not the self-hosted Checkmk Cloud Edition, right?
Correct, I want to know, if it is possible to connect Checkmk Enterprise on-prem to SAAS Checkmk Cloud.
Currently it is only possible to use the push agent to upload agent Output to the saas Cloud.
This will change in the future.
@troelsarvin Checkmk Cloud SaaS does not feature distributed monitoring at all. So no edition can be connected to it.
@aeckstein maybe I am misunderstanding your message, but the push agent is the default operating mode of Checkmk Cloud SaaS for monitoring classical operating systems.
@robin.gierse This was the short way to say, that there are currently no connection options besides using the push agent.
No distributed monitoring, nothing that can be connected onprem yet.
But I see that the answer was too short and misleading.
Some context:
We are building at the moment a “relay”, which acts like a remote site, but in a light-weight managed mode. Meaning that we have less dependencies between a central and more site. This is required as for a SaaS mode, the operation responsibility lies within Checkmk and we need to minimize dependency towards the remote setup. Not only from a version compatibility perspective, but also from a redundancy perspective. Remote sites store metrics etc., however a SaaS operation model requires central storage as we can’t gurantee otherwise for availability of data.
Thus, connecting current remote sites is not sensible and thus not allowed (even though it would be possible).
This is exactly what we need as well as MSP (we can’t realistically have VPN to all the clients sites and push mode doesn’t work for agentless SNMP monitoring)
@martin.hirschvogel
Could you please share a rough timeline for this “relay” configuration?
We are already working on it. It is our top priority.
With that said, it’s done when it’s done ![]()