danfromberlin

I usually just submit www.notlinked.in and it has worked fairly well.

Why does this site with its focus on a video player need to know my browser's location?

This seems sketchy.

I quote from your website: "Don't worry if you don't know what GitHub is, you only need to create an account." You don't appear to make any assumptions that your users understand that their notes will be published and readable by anyone on the internet.

Furthermore, your clarification: "Currently, Kobble stores all user data in secret GitHub Gists, under your account. Secret gists are not private." does not help because it does not explicitly state the fact that notes will be readable by anyone on the internet.

Hi dozzie [edit: typo],

I can entirely sympathize with your comment here, but I'd like to try to quickly present a contrary perspective:

Indeed there are architectural trade-offs made by every monitoring system, and icinga2 makes some that we also have found to be frustrating: one such example that comes to mind for me personally is that icinga aims to maintain backwards compatibility with its historically-derived nagios configuration file syntax which is difficult to understand and hard to parse in an automated fashion.

On the other hand, there are exampls of architectural choices that I believe icinga gets right: It implements an approach to secure and authenticated metrics collection that virtually every other monitoring system leaves as an "exercise" for the user. It provides checks and alerts and notification thershholds by default, which many other monitoring systems don't.

We build monitor in a box to attempt to highlight one particular approach to using icinga 2 which we find works for us. We attempt to be systematic and through in our approach, aiming for a reproducible, Ansible based implementation that emphasizes modularity and code reuse. We invite everyone to try out our open source offering to decide for his or her self whether the benfits of running icinga 2 in this fashion outweigh the drawbacks.

Hi Kristopolous,

In a nutshell, Monitor in a box is a system/application monitoring solution based on Ansible, Icinga 2 and Grafana.

I would like to kindly point you to our demo to see what our software does.

We've also made our code available at github, and I invite you to check out our README to get an idea of how to begin using.

I hope that helps clarify what we're trying to do.

Hi sagichmal,

To be precise, Monitor in a box is a solution built in-part on Icinga 2.

Hi VA4FXP,

I'm sorry about that. We'll see what we can do to address this problem.

Hi zbjornson, regarding your question about "Wondering what the free version uses if it doesn't include graphite for dashboarding": the answer is that free version just includes the icingaweb dashboards and not those implemented with grafana.

Also I'd like to clarify a possible misunderstanding: Monitor in a Box does not require that ansible be installed on all the servers. We only require that ansible be installed on the one machine that orchestrates the setup of Monitor in a Box.

Who else feels a sense of horrible dread and frustration that every minutiae of my (and your) online activity is recorded for eternity and exploited to the fullest extent?

What are you going to do about it?

This quote doesn't inspire so much confidence:

“The thing we were terrified about when switching over to PC’s, was learning Windows, but it wasn’t as bad as we thought, especially because we spend the majority of our time in Adobe® Premier Pro and the interface is exactly the same.”