I would love to read more about your product/service/idea.<p>But I can't.<p><a href="http://contrastrebellion.com/" rel="nofollow">http://contrastrebellion.com/</a><p>Being visually impaired just makes things worse. Your site doesn't work with FireFox 'Reader View', and that forces me to 'Toggle CSS' off which causes the icons and site-design to be FUBAR.<p>You might have the best damn product in the world, but if I can't read about it on your own pages then it's no good to me.<p>I only found out that you use Ansible from the comments on here from another poster. I really want to know about this now as I have migrated our entire datacenter to Ansible, and I really love it.
I'm impressed with this project's messaging and support/feature pricing structure. I think trying to find more sustainable models for funding open-source software is interesting, and I don't recall seeing this exact approach used before (i.e. free version w/o LE or Graphana support). It'd be amazing if a percentage of each support contract gets donated back to upstream projects like icinga2, Graphana, and LE.
Very interesting. As one of the sufferers who struggled many times with setting up icinga2 with distributed (and SSL-Encrypted) monitoring, this automation takes a way a lot of the hassle. I think it is one step in the right direction. Reminds me with: <a href="https://mailinabox.email/" rel="nofollow">https://mailinabox.email/</a>
Wondering what the free version uses if it doesn't include graphite for dashboarding. It also feels way more invasive to have to install Ansible on all of my servers instead of just statsd plus a config file to point it at a host. (Edit: it's not required.)<p>Nice to have a supported, pro-grade monitoring product that isn't priced per server, finally.
Is it just me or do these pitch pages always seem very light on what the software actually does... does it aggregate logs? LD tweaking maybe? Is it a kernel module? What is this technology?
Honestly, fixing Icinga's broken architecture (shared with Nagios, Shinken,
Zenoss, and Zabbix) with a bunch of shell and Ansible scripts doesn't seem
like very robust solution.<p>And install instructions from README on GitHub looks like one big let's not,
with half a dozen of modernish tools that obscure what's actually happening
(basically, `apt-get install icinga2' and putting some config files in place).
Really nice setup, I'm glad to see Ansible being used to orchestrate the machines. I really do like that system for it's ease of use and low learning-curve.
As someone from the Windows world, I'm always surprised to read things like:<p>"That said, the more specific you customize your monitoring, the more detailed an understanding of these components you will need."<p>This sounds as bad as what I've heard about Nagios. Why does it have to be so complicated?