Distributed monitoring ends in community/raw version?

[RMS]

Hello,

In your web page under Checkmk pricing, I see that Distributed Monitoring is not supported in the Community/Raw version—only in paid versions. However, the comparison table indicates that Distributed Monitoring is supported in Community versions.

Is this a typo, or will Distributed Monitoring become a paid feature in the future?

[kbuettner (Konstantin Büttner)]

My money is on typo, but some clarification would be good. (I’ve never seen a feature being discontinued from the community edition)

[burgeau (Mark Burgess)]

Had the same discussion the other week with a customer.

Distributed monitoring is still in Community edition in 2.5:

I haven’t had a chance to setup the remote site under Community 2.5 yet.

Will do that and put a blog up on what the differences are between Community v Pro/Ultimate for distributed monitoring.

[andreas-doehler (Andreas)]

Differences should be the same as before.

• no liveproxy

[RMS]

Dashboard sharing in version 2.5 is limited to 30 days. I’m not sure whether previous versions offered unrestricted dashboard sharing or if this limitation already existed.

Checkmk 2.5 dashboards - expiration date for public links

Just upgraded checkmk raw from 2.4 to 2.5.0p6. One question about sharing dashboards: why public links can be created only with a 1-month or less expiration date? There’s a “Set expiration date” checkbox, but it’s selected by default and not clickable (it’s grayed out). How can I share public links to some dashboards with no time limit?

In my 2.3 infrastructure, I’m now seeing ‘Upgrade to Pro’ buttons in ‘Schedule Downtimes’ and ‘Acknowledge Problems’ to activate certain features. This doesn’t concern me much since I’ve never used these features before. However, I’m worried that Checkmk community/raw edition might be moving towards a limited model.

[Yggy]

@RMS

I’m not sure whether previous versions offered unrestricted dashboard sharing

AFAIK: the feature doesn’t exist in my 2.1 raw. I can only make dashboard available to other users, but not share public links to dashboards.

[andreas-doehler (Andreas)]

@RMS

Dashboard sharing in version 2.5 is limited to 30 days. I’m not sure whether previous versions offered unrestricted dashboard sharing or if this limitation already existed.

This is a new feature not existing before.

@RMS

In my 2.3 infrastructure, I’m now seeing ‘Upgrade to Pro’ buttons in ‘Schedule Downtimes’ and ‘Acknowledge Problems’ to activate certain features. This doesn’t concern me much since I’ve never used these features before. However, I’m worried that Checkmk community/raw edition might be moving towards a limited model.

This feature was all time time enterprise/pro only. This only applies to recurring downtimes not the downtimes or acknowledge at all.

[RMS]

Hello Andreas,

I don’t want to be too concerned about this. I’ll mark your previous answer as a solution.

Thanks

[marbaa (Marek Babinčák)]

My notes:

At the moment I’m configuring enviroment with Community edition 2.5.0p8 Docker with notification sending to Opsgenie. Distributed monitoring is available, have 14 satellites now, more to come. However in Community edition there is no available sending notifications to central instance. So it is needed to setup Opsgenie integration on each satellite.

Setup is for monitoring up to 1000 Supermicro RTX PRO 6000 and Nvidia DGX B200 servers over redfish. Nagios core in Community is really weak and is make insnane load on satellite VMs compared to paid version.