Advertisement
Tag Archives: monitoring

October 2016, “Community Choice” Project of the Month – Nagios Core

For our October “Community Choice” Project of the Month, the community elected Nagios Core, a powerful, enterprise-class host, server, application, and network monitoring tools. Ethan Galstad, creator of Nagios Core shared some thoughts about the project’s history, purpose, and direction.

SourceForge (SF): What made you start this project?
Ethan Galstad (EG): Nagios was inspired when I was working as a system admin at my college newspaper. We didn’t have any type of monitoring solution in place and got burned when the IT staff was at an offsite meeting, completely unaware the servers at the newspaper had crashed. The idea for Nagios was originally born then. Coding on Nagios proper didn’t start until a few years later when I was interested in starting a business that would offer monitoring services.

SF: Has the original vision been achieved?
EG: I originally only thought a dozen or so people would have an interest in Nagios. Since its first release in 1999, the popularity of Nagios has skyrocketed beyond my wildest imagination!

SF: Who can benefit the most from your project?
EG: Sysadmins, network admins, devops – anyone who’s technical and has a need to monitoring their infrastructure – regardless of whether that’s workstations, servers, networks, applications, or services.

SF: What core need does Nagios fulfill?
EG: The ability to know what’s going on within your system so you can focus on other tasks in your job. The last thing a busy admin wants is to be the last to know that a critical server, website, or application has crashed without their knowledge.

SF: What’s the best way to get the most out of using Nagios?
EG: Nagios Core is a pretty technical project, so taking the time to read the manual is a must. There are numerous tutorials and videos online that provide helpful tips and best practices for new people that are looking to deploy Core in their infrastructure.

SF: What has your project team done to help build and nurture your community?
EG: We spend quite a bit of time incorporating the community’s patches and feature requests into releases. Several years ago we launched Nagios Exchange (exchange.nagios.org) to highlight the massive development effort of the community. The site features a plethora of addons the community has developed for and around Nagios Core.

SF: Have you all found that more frequent releases helps build up your community of users?
EG: Frequent releases is a cornerstone of Open Source development, and Nagios Core is no different. Each time we make a release we get valuable feedback and feature requests that go into future development efforts.

SF: What was the first big thing that happened for your project?
EG: The first important thing would be the initial developers that joined the project many years ago. Their insight, guidance, and development efforts helped make Nagios into what it is today.

SF: What helped make that happen?
EG: Publishing the Nagios Core project on SourceForge was extremely instrumental in bringing in developers. Thanks for the awesome services you guys provide! Without a doubt! SourceForge is the place to be for Open Source projects.

SF: What is the next big thing for Nagios Core?
EG: More optimization and performance improvements. People always seem to push Nagios Core to larger and larger environments. Right now we’re working on a new feature that leverages gearman to distribute checks. In the testing we’ve done, we’ve found the performance improvements to be incredible.

SF: How long do you think that will take?
EG: We’re hoping for a release by the end of the year. It might come sooner, but we’re working on a number of other feature requests at the same time, so it’s difficult to say for sure.

SF: Do you have the resources you need to make that happen?
EG: Yes we do, but contributors to the development efforts are always welcome!

SF: If you had to do it over again, what would you do differently for Nagios?
EG: I’d probably pick a language other than C for the main project, for the sole reason that it’s easier to find developers to join in. C is great for speed and optimized apps, but it’s got a bit of a higher learning curve than some other languages.

SF: Is there anything else we should know?
EG: I think that’s it for now!

[ Download Nagios Core ]

Pandora Flexible Monitoring System


Rich: I’m speaking with Sancho Lerena, and we are speaking about the Pandora FMS Open Source project. And we’re also speaking about the company behind Pandora FMS.

If you’d like to have your project featured on the SourceForge podcast, just drop me a note and we’ll schedule something.

If the embedded audio player below doesn’t work for you, you can download the audio in mp3 or ogg formats.

You can subscribe to this, and future podcasts, in iTunes or elsewhere, at http://feeds.feedburner.com/sourceforge/podcasts, and it’s also listed in the iTunes store.

Tell me how this project got started initially.

Sancho: This began about 8 years ago. I was working in a bank as a security consultant, and I had a lot of spare time. I was working with firewalls, with all systems like BSD, Solaris, AiX. I need to monitor different things – strange things – in that system. And with the usual tools from the big ones like Tivoli and HP – it was pretty difficult to extract information from that system. So I started with a few scripts that just collected data and sent it to me, and the thing started to grow up as an experiment for my day to day work, and after a year or two, the whole thing was something more than a few script. Later I have something – a product which was useful to monitor different kinds of servers – unix servers, Windows servers – I started to monitor network equipment. So I thought that could be something I could do for a living, and I started a company with that idea.

Rich: How is the open source edition related to what you do for your company? Are there some things that you add to that in an enterprise version?

Sancho: The most difficult part of the project was how to make profit from an open source project. So at the first versions, until, I think it was in 2007 or 2008, the product was 100% free. Free as open source, and free for people to pay nothing. We saw in that period that it was very difficult to earn money, mainly because – not because of the license – big companies don’t trust you if all is open. It doesn’t seem professional – for some of them, not for all, but I think it’s difficult. So we focused our strategy to identify what parts of the product will be useful only for big companies. So, our enterprise features are only for big companies. It’s not the same to monitor a small company with 20 servers than to monitor 2000 servers. It’s completely different. So, in Pandora FMS I think 80 or 90% of the features are open. Everybody can just download the package and install and use it. There are thousands of servers using the Open Source. But companies like Telefonica, or other companies in Japan like Rakuten, or Casio, need something specific to monitor a lot of systems in a homogenous way. We call it policies. Probably there is a lot of other applications which use the same approach.

Rich: Where did you get the name for the project? Is it related to the greek myth, or is there some other history behind that?

Sancho: Yeah, that’s it. You need something to warn you if something wrong escapes from the unknown. You need to know. The first logo was an octopus inside a box. Later we added the ‘FMS’ – because “Pandora” is too generic, and it was difficult to search in Google. The ‘F’ initially was for ‘Free Monitoring System’, but someone told me that ‘Free’ is a bad marketing word, so we renamed it as ‘Flexible Monitoring System.’

Rich: How does Pandora compare to some of the competition out there like Nagios?

Sancho: We like to think we are better. The real thing is that the Nagios community is huge, and everybody, when you ask, how do you do monitoring in your company or in your experience, everybody thinks Nagios, because Nagios was the first, or the first in importance to the community. I believe Nagios is not evolving in the same way we do. I think the user interface, and letting the user have the complete power from the console, and not need to enter into screens, or start a process from the shell – it’s very important. And also reporting. It’s one of the most important difference between other solutions and Pandora. Monitoring is very very complex. There’s more than 100 applications for monitoring in the market. There’s a lot of differences between each of them. We like to think Pandora is a horizontal approach, that means you can use Pandora for almost any kind of environment you need. Networking, servers, performance, business applications, reporting, even data mining. Of course, you can integrate all the pieces together. Other applications more focussed on performance, or availability, or even management. Pandora likes to put all these features together.

Rich: On the community side, how involved is the community in the development of the code? Is it primarily your company that develops the code, or do you also have participation from an outside community.

Sancho: The first time we started Open Source, we had some developers who were involved in the project. We have a few developers from the US, another one from Europe, another one from New Zealand. But the kind of development help they provided was only for small features, and not for long-time commitment. More like – I think that feature is OK and I would like to help you do that, or give us suggestions, or bug reporting. Later, when we moved to a more enterprise level, trying to focus on the features big companies need, we lost that kind of contribution, but in exchange we got in contact with companies which were interested in helping us to adapt Pandora to their needs. At this moment we have a full committer relationship, not only for development issues, also about business relationships, with a company in Japan, one of our partners. They have six people in their development team. All of them have access to the repository code. and we have also a company in Ecuador who are helping us also with some development. And we increase a lot of people giving us suggestions, ideas, and of course bug reporting. We have a very populated tracking server – Very active.

Rich: What is in the future for your project? What sorts of new things are you looking at doing in the coming year?

Sancho: We are now working in two different versions. We call it the stable version – we’re probably releasing any time now. It contains just a few new features and a lot of bug fixes, like usual in this kind of development. But we are working also in the next minor version – version 5.2. We are doing now a lot of huge improvements. We are adding the NetFlow feature to Pandora, for free, for Open Source. And we also are adding a new layer for management of different sites of Pandora. We call it metaconsole. We’ll provide a service provider to offer monitoring services to other companies, and be able to manage, why not, 10,000 servers from a single console.

One of the first things I had clear when I started Pandora was that the product should be on SourceForge. Because SourceForge was, for me, the source of knowledge about Open Source projects. It’s the site to be on – to be there. At first we had problems with the product name because it was taken. I had to wait two years until the Pandora name was free again. That’s because your site is really important on the Internet. If it’s an Open Source product, it should be on SourceForge.

Rich: Thank you Sancho for taking the time to speak with me.

Sancho: Thank you too.