Slashdot Mirror


Nagios-Plugins Web Site Taken Over By Nagios

New submitter hymie! writes "Nagios is a commonly used IT tool that monitors computers, networks, and websites. It supports the use of plug-ins, many of which were developed independently by the community. Holger Weiß, formerly of nagios-plugins.org, announced that 'Yesterday, the DNS records [of nagios-plugins.org] were modified to point to web space controlled by Nagios Enterprises instead. This change was done without prior notice. To make things worse, large parts of our web site were copied and are now served (with slight modifications) by Nagios. Again, this was done without contacting us, and without our permission. This means we cannot use the name 'Nagios Plugins' any longer.' Further discussion is available in a Bugzilla thread."

39 of 119 comments (clear)

  1. Shitting all over your most supportive users by Anonymous Coward · · Score: 5, Insightful

    is not a viable long term strategy.

    1. Re:Shitting all over your most supportive users by Anonymous Coward · · Score: 5, Informative

      No, but Nagios hasn't cared much about it's users for some time now. It worked when they were the only game in town[1], but these days you can choose to use Icinga or even Sensu; both of which are far better products than Nagios and support Nagios plugins.

      [1]: Well O.K, there's OpenNMS, but that's network oriented rather than infrastructure so it's not a direct comparison.

    2. Re:Shitting all over your most supportive users by aliquis · · Score: 2, Funny

      Shitting all over your most supportive users (Score:5, Insightful)
      is not a viable long term strategy.

      Apple: - What?

    3. Re:Shitting all over your most supportive users by Anonymous Coward · · Score: 2, Funny

      Shitting all over your most supportive users (Score:5, Insightful) is not a viable long term strategy.

      Apple: - What?

      You're holding it wrong.

    4. Re:Shitting all over your most supportive users by Anonymous Coward · · Score: 3, Insightful

      Give Zabbix a try, you'll be surprised. Much better flexibilty and easier to tie into active directory for authentication.

      http://www.zabbix.com/

    5. Re:Shitting all over your most supportive users by jon3k · · Score: 3, Informative
      http://www.zabbix.com/license.php

      If you use ZABBIX in a commercial context such that you profit by its use, we ask that you further the development of ZABBIX by purchasing some level of support.

      Just fair warning.

    6. Re:Shitting all over your most supportive users by deadeye766 · · Score: 2

      IMHO stay away from Zabbix for anything but small-ish environments. For what it's worth, our experience hasn't been great running zabbix in a distributed configuration. Plus, there isn't much flexibility in terms of configuring checks on hosts due to the way templates work.

      Also, their "enterprise support" is a fucking joke. Our support experiences are "chatting" back and forth in a Notepad while a guy fucks around in the mysql DB for a few hours. Total waste of money. =(

  2. Copyright violation. by Anonymous Coward · · Score: 2, Interesting

    This sounds like a plain and simple copyright violation in many ways.

    Sue Nagios.

    1. Re:Copyright violation. by Anonymous Coward · · Score: 5, Funny

      Sue Nagios.

      Are you related to Sally Nagios?

    2. Re:Copyright violation. by gl4ss · · Score: 2

      well yeah but the understanding was that the domain would point to the monitoring plugins...

      now nagios altered the deal.

      --
      world was created 5 seconds before this post as it is.
    3. Re:Copyright violation. by xQx · · Score: 2

      Yeah, and that would hold weight if you weren't using their trademark all over your site.

      Seems to me this is just an occupational hazard of using somebody else's name for your site.

    4. Re:Copyright violation. by xQx · · Score: 5, Interesting

      This battle was lost years ago when this volunteer organisation gave control of their domain to Nagios Enterprises to avoid trademark issues.

      So they've been able to continue in their priviliaged position paying Nagios Enterprises SFA for theses years, until finally some mid-level bureaucrat decided that the money they were getting ($0) from nagios-plugins.org community group doesn't outweigh the brand-risk that they pose, and they brought the website back inhouse.

      Wow, I would never have seen that coming!!

      Sounds to me like Nagios Enterprises is readying its self for sale.

      This is the open source business model. Cisco have been at it for years. Get used to it.

    5. Re: Copyright violation. by cyber-vandal · · Score: 5, Funny

      Pray they do not alter it further...

    6. Re:Copyright violation. by tverbeek · · Score: 5, Insightful

      You seem to be completely overlooking the issue of copyright. Re-appropriating the domain was apparently within Nagios' rights, but copying the contents of the web site was not. Trademark rights are not virally transmissible to copyright.

      --
      http://alternatives.rzero.com/
    7. Re:Copyright violation. by shentino · · Score: 2

      Changing dns and copying a website are two entirely different things.

    8. Re:Copyright violation. by mysidia · · Score: 4, Informative

      Yeah, and that would hold weight if you weren't using their trademark all over your site.

      I think you don't get it... the Nagios Plugins project pre-dated Nagios. The Nagios Plugins Project was renamed from The NetSaint plugins project due to trademark issues. Nagios was an acronym for "Nagios Aint gonna insist on Sainthood"
      The open source project was using the name before Nagios Enterprises was founded, and these development teams, therefore have prior use of the name Nagios.

      They were apparently tricked into handing over control of the domain to the guy who founded Nagios enterprises later.

    9. Re:Copyright violation. by davester666 · · Score: 2

      Copyright violations only count if you can afford good enough lawyers to enforce the penalties.

      --
      Sleep your way to a whiter smile...date a dentist!
  3. Switched to Icinga a long time ago by Anonymous Coward · · Score: 3, Informative

    So far I have not looked back once.

    1. Re:Switched to Icinga a long time ago by Anonymous Coward · · Score: 2, Insightful

      +1

      The switch is trivially easy and all plugins are backwards-compatible. The "classic" UI has every annoyance of Nagios UI fixed. There is a sensible release cycle and authors that accept feedback in their bugtracker.

      Every time I hear people complain about their Nagios love/hate relationship I tell them to switch.

  4. Re:similar by Richard_at_work · · Score: 5, Informative

    Looks like Nagios Plugins was a community project to provide plugins for Nagios, with little to no input by Nagios themselves. At some point in the past, the website name was transferred to Nagios to avoid trademark issues but the project continued to be community driven and led. Now, Nagios has redirected the DNS to its own plugins website, forked the community codebase, setup an entirely new developer base and taken the company line that "monitoring plugins (the name chosen by the original nagios-plugins project leads) is the fork, not us".

    Reading the propaganda by the Nagios rep on the bugzilla thread is highly amusing, smacks of Eurasia and East Asia from 1984.

    If all of this is even mildly true, its quite an evil thing by Nagios to do.

  5. Re:Suprise, not really by paziek · · Score: 3, Informative

    They (Nagios Enterprises) requested it. I didn't see mention of why they did, but I would guess it was trademark issue. They were supposed to let them use it independent of Nagios Enterprises, but seems like 3 years was all they could get on this deal. From what I read in their discussion, reason for takeover are mentions of compatible competition on main site of old Nagios Plugins.

  6. Distro packaging mess by paziek · · Score: 4, Interesting

    It will be interesting to see who will provide source for packages used by various distros. Those plugins can be used by other monitoring applications and I guess that new maintainers on the old domain could release version of their plugins that would not work with competition, while at the same time old maintainers probably shouldn't use nagios-plugins for their packages.

  7. Re:Not a registrar problem. by Anonymous Coward · · Score: 3, Informative

    So really the company just decided they want control of the server now instead of pointing their domain to a third party. Nonstory.

    You apparently decided to read the article on this occasion, but inexplicably stopped after the second link.

    3.3/10 for effort but could try harder.

  8. Re:Not a registrar problem. by Richard_at_work · · Score: 5, Informative

    The story is a but more than that - they took the website almost as-is, forked the codebase and are portraying themselves as the original project with a new developer base, insisting the original developers are the fork.

    If they had switched the domain to a brand new website and started from scratch, that would be your non-story...

  9. Re:similar by Splab · · Score: 2

    It's quite a mess they have made, they expect us (the users) to just accept a new team under same name.

    Well fuck that. Hope package maintainers are on top of this and make sure users are forced to make a choice of which plugin distribution to use.

  10. The real question is why. by leuk_he · · Score: 2

    Why did nagios take out the server out the hands of the community. Was there a fight in the community? Is this just a "it is named nagios, so it is ours"? Want do to some subscribtion? Sombody in the community took to big consulting fees?

    At first it looks like that nagios has a name to loose, and more work to do by maintaining a lot of plugins and a extra site.

    1. Re:The real question is why. by rnturn · · Score: 2

      While I hate to comment on a grammatical post... I, too, am getting more than a little tired of seeing this misuse in a comment by someone who, otherwise, seems to have a good grasp of the English language. Whenever I see it, my respect for that poster's argument/comment drops by about 10dB. They may as well have posted in all caps.

      --
      CUR ALLOC 20195.....5804M
  11. Alternatives... by ptudor · · Score: 2, Informative

    After having the good fortune to spend a few weeks testing everything free, I've got to spend a minute evangelizing for Zabbix.

    It took me a week to understand the concepts, but the clone button and templates make Zabbix my favorite tool. The local Zabbix agent on each host gives detailed metrics and the screens of graphs are great.

    Check out the appaloosa-zabbix-templates for more MySQL and Memcache charts than you ever thought might work out of the box.

    Zabbix is ridiculously powerful, from auto discovery on subnets, to simple ping and snmp, up through more advanced tools.

    1. Re:Alternatives... by Anonymous Coward · · Score: 2, Interesting

      Nah - it was way before 4.0.

      The core Nagios guys pissed off enough people that various forks had appeared (e.g. Icinga, Shinken etc), and the new forks provided an outlet for years of repressed development/feature ideas that were squelched in Nagios as 'not part of the core of what we do'.

      And as these other projects gained steam and became more popular, the core Nagios folk realised they had some major catch-up work to do, which (iirc) is where 4.0 came from, and seemed to take a bunch more major contributors on board around then as well.

      (But they also had a bit of a kerfuffle a yeear or two back over a similar thing - the project going a bit too far in the direction of comercial control (aka stranglehold)).

    2. Re:Alternatives... by michael.friedrich · · Score: 5, Informative

      The funny thing is, that Nagios Enterprises didn't write Nagios 4.0 - that work was done by Andreas Ericsson who works for op5. So instead, you should call "Nagios 4 Core" "op5 Core" if you're looking for the who-did-write-it. The sad thing is, that Nagios Enterprises kicked out Andreas Ericsson out of the Nagios core development after recognizing that people actually knew that Andreas was the only core developer at that time - working for a competitor. Andreas forked Nagios 4 into Naemon abandoning the dictatorship by Nagios Enterprises. You may find their website interesting but there more interesting read is located here in terms of the Nagios Plugins project: https://www.monitoring-plugins.org/archive/devel/2014-January/009432.html If you're interested in more details, the announcement happened on last years OSMC http://www.youtube.com/watch?v=YgbbyyNIiHc So other than the clusterfuck by Nagios Enterprises in regards of lying to the community again, they've lost their last core developer and there are fellow forks around the corner filling the gap. If you're questioning yourself - I am the lead core dev of Icinga, but what's written here is my sole personal opinion.

  12. Somone had to plug icinga by Anonymous Coward · · Score: 3, Interesting

    Someone had to plug the better open source monitor. Icinga (https://www.icinga.org/) is either a fork from nagios 2 or a rebuilt but either way has config file level compatibility with your nagios configs. A way saner architecture for writing add-ons and a better web ui.

    1. Re:Somone had to plug icinga by michael.friedrich · · Score: 3, Informative

      Actually Icinga was forked off Nagios 3.2.1 and some patches ahead. Meanwhile we've ported plenty of Nagios patches, but also sent them Icinga patches. At some point, they've removed the Icinga copyright on those patches, and banned me from their bug tracker. But since people had been asking quite often, which patches and features are exclusive to Icinga, I had compiled a periodically updated table with all details exposed. https://www.icinga.org/2011/11/03/icinga-vs-nagios-a-developers-comparison/ And while we're still working on the 1.x branch, we're preparing Icinga 2 and Icinga Web 2 for their first final releases, overcoming long lasting problems (such as an integrated cluster stack, or recurring downtimes).

  13. Just eastablish a new fork by mlwmohawk · · Score: 2

    Nagios is a stupid name, and now they are acting like a stupid company. You can't buy good will, but you can certainly spend it out of existence. Create an entity sys-monitoring.org, or something, pull a GPL nagios, change trademarks, and point to monitoring-plugins.org. That really is the only way to deal with companies that behave this way.

    Then contact Debian, RedHat et. al. they will probably deal with the new fork after this crap.

    1. Re:Just eastablish a new fork by houstonbofh · · Score: 2
  14. Re:Not a registrar problem. by causality · · Score: 2

    Dick move? You better believe it. Piss off a sizable community? Hell yes. Perfectly legal? Yup. The right way to do it to avoid future liability? Unfortunately, most likely.

    That reminds me of a saying I once heard: "we will have world peace when the last lawyer is strangled with the entrails of the last banker."

    --
    It is a miracle that curiosity survives formal education. - Einstein
  15. Plugin developers by MouseTheLuckyDog · · Score: 2

    In the future plugin developers should make their plugins compatible with alternatives but incompatible with Nagios. Then Naagios can either live with the old plugins or hire people to port the new plugins. Then Nagios can see what the community meant to them. This is a typical business approach which says that the enemy is not your competitors but your user community and the community of people who add value to your product. Time these users got a clue.

  16. Re: Creepy? by rnturn · · Score: 2

    Creepy? Howzabout "disgusting"?

    IANAL but I doubt there's anything in trademark law that would allow the Nagios team to appropriate the work of the Nagios Plugin team wholesale the way they did and merely change the name of the team members. While I hate the term, this looks like it could be a blatant example of ``intellectual property'' theft. Was the Nagios team unable to come up with their own wen site? Really? Rights to the domain name don't give you rights to the work that went into creating the plugin web site.

    After having used it for 6-7 years, Nagios just went off my list of recommended monitoring tools. Icinga just moved to the top.

    --
    CUR ALLOC 20195.....5804M
  17. From the bugzilla thread by rk · · Score: 4, Insightful

    "nagios-plugins is not a fork, but a rebase with new team members. monitoring-plugins is indeed a fork, as their new name suggests."

    That is rich.

  18. Re:similar by houstonbofh · · Score: 2

    If all of this is even mildly true, its quite an evil thing by Nagios to do.

    It sure puts a new spin on the Nagios Enterprises side of the Icinga fork... So, who still thinks Icinga was making stuff up?