Centreon Reviews

We use it for monitoring infrastructure and custom applications. We customize the monitoring and dashboards. We have a NOC here, where we monitor our clients' environments 24/7. It is integrated with our ticketing system and SMS and email for communication. We also have a Knowledge Base system integrated with Centreon.

We use it on-premises for ourselves and we provide SaaS with it for our customers. We have more than 20 installations of Centreon.

Centreon makes it easier and quicker to get the information needed to analyze. It uses different colors when there is a problem that passes a threshold. It gives you information and you just have to analyze the machines on the report. It's easier to find the ones we need to comment on to our clients, so they can look more deeply into them.

The solution also increases the accuracy of our monitoring because the plugins enable us to monitor things that we wouldn't normally monitor. There are built-in plugins that pick points that we wouldn't usually monitor if we had to create that monitoring by ourselves. When monitoring something, we might not consider one of those points, because it's not a main point. But it is being monitored. And when we troubleshoot, sometimes we use one of those monitoring options that gives us more information. That makes us more accurate. Our accuracy could always increase, of course, but there is no limit on that.

With the automated configuration for monitoring items using plugins, we optimize our time. And with integration, if we have something happening, we can automatically open a ticket and send communication through SMS or email. Both are very good options. During the day it probably saves us 50 percent of our time, and during the night it's even more. 

We usually do a mapping of our client's business and present that on a dashboard. We don't generally use the reports for that because the dashboards are more real-time. That way, the client knows in real-time what's happening. That helps align IT operations with business objectives a lot. Monitoring and presenting in that way is the whole point.

In terms of mean time to resolution, when we introduced Centreon into operations that didn't have it, it reduced the time to resolution because we located the source of problems quicker. The amount of time really depends on the stuff involved. There are a lot of links that take many hours. The time that is really reduced is the time for detection of the problem. The total resolution time, which contains the detection time, is reduced because of the detection phase. But the resolution phase is basically the same. The overall time varies a lot. It's hard to say how much it reduces the MTTR. But it can be very significant in cases where detection is difficult.

We use almost everything in the product. What is most important are the monitoring, alerting, and the dashboards. If we don't have basic monitoring, we don't have a NOC. It's the basis of the functionality of the system. 

The dashboards are valuable because they ease troubleshooting and viewing. It becomes easier to locate the source of a problem. We can use BAM for that as well, but we only have it in one of the installations, one that has the Centreon Business edition; the others are using the free version. The dashboards make it easier to communicate with our clients. They don't want to see the alert console, they want to see a beautiful dashboard representing their network and their business and to watch it in case something is wrong in their environment.

We use the reports, but not that much, although the reporting is very good. We use it for creating books, monthly reports for our clients. We use the reports for analysis and to say, "These ones require growing," or "This is too big. You can lower the memory and save some money on your cloud." That is a monthly service we provide to our clients. 

Centreon is also very versatile. There are a lot of built-in plugins that ease the work. But if we need to connect to some device that doesn't have a plugin ready, we can customize a plugin and create monitoring for the device ourselves. It's quite easy. When there is a plugin, it speeds the implementation of new devices. If there isn't one, it takes a little longer, but we are not unable to monitor the device. We are always able to monitor.

I would like to see more plugins. That is something it needs. 

There is also room for improvement through dynamic thresholds, or self-discover thresholds. 

I would also like to see a discovery feature that could map the whole network environment and automatically suggest things. 

Finally, NetFlow would be helpful. We have a lot of clients that ask for NetFlow.

I've been using Centreon for more than 10 years.

It's very stable. We have had Centreon here for more than 10 years, and we have had about three problems in that time.

It's very scalable. We have installations with more than 10,000 pieces of equipment. We use the free version and it works well. You just add more pollers and segregate the database.

Their technical support is very good. They answer quickly without any problems. It's a good service.

We used to use Nagios. I also used the IBM Tivoli solution, OpenView from HPE, and WhatsUp Gold. I have used many solutions.

We switched to Centreon for a number of reasons. The IBM and HPE solutions were too expensive. We then went to a free solution, Nagios. But the Nagios interface is not as complete or as good as Centreon's interface. So we switched to Centreon's free version first and moved to using the EMS solution about a year ago, to get the benefits of plugins and dashboards.

The setup is very easy. Centreon itself is an ISO that you boot. You answer some questions and it's up and running. In terms of configuration, you can put in the IP address of the host and attach the plugins and they are ready for monitoring. It's very easy. If it had a more complete discovery feature, it would be even better, but it's already very easy.

The time it takes for the initial deployment depends on how many hosts, and how deeply, you want to monitor. But in less than a week, you can have good monitoring set up for a small to medium sized company. The longer part for us is the interview with the business, the analysts and the system analysts, to understand their particular applications and services and the impact of those on their business, to create business dashboards and business monitoring.

We have had a quick return on investment because we have a lot of hosts to monitor. For new implementations it speeds up the process of deploying. That is labor-intensive work, and it reduces the amount of that work. That helps create a return on the investment quickly, by not spending on as many man-hours as we would have.

In terms of replacing other tools, it hasn't really reduced our cost, but we have reduced costs with Centreon in another way. We need fewer people to monitor more stuff. Prior to Centreon we used free tools so the cost of the tool was not the issue; it was the performance of the people working with the tools.

If you need basic monitoring without dashboards, just monitoring, the plugins are very useful and really cheap. If you want a more complete solution with dashboards and reporting, the EMS solution is great and it is not that much more expensive. It's a good value. Really good.

We use multiple views on Centreon. We don't use a single view because it's too big. We could have a single view. But in terms of alerts, when we create dashboards that provide the best point of view for the whole infrastructure, we usually segment them to see things in more detail. If we put the whole infrastructure in a single dashboard, it would be too macro, it would not be detailed enough. 

We have a lot of screens for monitoring so we create a lot of dashboards and put them on the screens. Those dashboards are not super-detailed, but they are also not a single, macro view, so that we can know where a problem is. We usually create enough dashboards to avoid having to drill down. We have drill-downs, of course, but as a NOC, we prefer to have the most information we can have on-screen. For that we have a lot of dashboards open simultaneously. All together, the way we have set things up, it provides a single view, but with a lot of dashboards, not a single one. That's how we prefer it.

In our company, for monitoring, we have 12 people using Centreon. For support, there are about 20. As for the number of users who only use our Centreon dashboards, I really don't know because our clients have a lot of people. We have three guys who implement Centreon, customize the monitoring, create the dashboards; all of them do all these functions. They maintain the solution to make sure it's working well.

I would rate Centreon a nine out of 10. It needs those features I mentioned earlier. But, for the price, it's really a 10.

Our primary use case is for our customers and us (S&L). S&L is service provider for our customers. We use Centreon for our own monitoring, but mainly, it is used for our customers. We support our customers to build up monitoring with Centreon, monitor their infrastructure, obtain a view of their environment, and know about problems before they really matter. Because if you have some architecture, then you can react. If you don't react, you will have real problems in the future. To prevent this, you can use Centreon, as one of many examples. 

If you have different functionalities, like a mail flow or production hall, that you need to take care of, then you can visualize those into a map, and you will be able to see on the map where your real problem is. E.g., you have a big hall with different access points where need to locate the signal of disconnected access points. Then, you can currently see it on the map. It's not that complex, because you can easily take a look at the map and see it where the location is of the faulty device.

It is decentralized, which is better, because you can reduce the load from a single system. Also, you get a better view because it's more independent. Then, for the management, it's nice because they have one central system. With that, they can manage all the other systems, as well. This means they don't have to configure each system by system. They can configure it from one single interface.

One good feature is you can see a big picture of your entire infrastructure. If one component is not reachable, this doesn't mean that you have other hosts which are not reachable, and you can see the cause of it. You can see the reason why your servers or program aren't available to the public. Therefore, you can solve the problem and save a lot of time in detecting the problem, so you don't have to search for it. You can see the problem right in the traffic interface. 

Another thing that is very powerful in Centreon is the possibility to use third-party modules. You can integrate different modules into it, so you can use the collective data in different ways for different needs. You can also create some events with it for support tickets, which is great stuff. You can automatically create some support tickets to support your IT department for an efficient way to work.

The data visualization features are great because you can get a view of the past. You can see some concurrent data correlations, because you can see your data usage over the past couple of weeks or months, so you can do capacity planning for the future. E.g., for capacity management, if you have to expand your storage, then you have more possibilities to use third-party modules or you could also buy a commercial one, like Centreon MBI, which is an enterprise feature of Centreon. Using the module, you can create reports automatically. Another benefit could be to use Centreon BAM because there you can design business cases and define KPI to get notified in a special way of escalation (first-, second-, third-level support.)

The great thing about Centreon is that it is also based upon Nagios. However, Centroen also provides the EPP, Enterprise Plugin Pack. The plugins are capable of monitoring nearly all data you want. The only necessary thing to get to your goal is it needs the destination that you want to monitor. This means you will have to have an API or some other way to make a call to the destination, so the destination can respond to it. If this is possible, you can nearly monitor all things with Centreon. This is very nice because you can monitor technical stuff and also normal things, like availability of some services, which are being used by your customers, your colleagues, or yourself, so you may get a view of the functionality behind it.

Centreon is not just a monitoring system, because if you take care of it, you will get great documentation and an overview of your topology without spending additional time to create or achieve that goal.

Because the API is available, which is good, Centreon could be more productive if there was better API functionality. Since you can automate some tasks with the API, such as how to add an host or automatically rollout a new host, this is a good area to continuously improve. E.g., the automatic adding of hosts, like LDAP objects or network scans. I think the network scan is a good point, because if you install Centreon as a fresh install, it's pretty easy to make the basic installation. It's very easy because you can download a ready-to-run image from a virtual machine. Or, you can also download a custom operating system on it and can get the system quickly running. However, after you have it running, you need to fill it with objects, which make sense. This is the point where Centreon could improve. They could add different tools to make it easier to add some hosts to your network from your Active Directory, etc.

Another big improvement would be a more powerful API to add host services, etc. At the moment, these things are possible, but not directly. These are things Centreon may need to think outside-the-box about and be creative.

Also, Centreon supports officially 10,000 services per poller. That is not much for larger customers, because this limit is reached very quickly. We use it with three times the limit without any problems, but Centreon says, "Okay, we are only supporting it with 10,000 services." We are aware that increasing the limit has different impacts because they need to support it. However, for most customers, it would be be very good if they could increase the limit of services.

I would also like to see an improvement of the communication with big data systems, because Centreon is a monitoring system. In our point of view, Centreon should be a part of a source for a big data system, not a big data system itself. So, it should be easier to add data from the Centreon system (monitoring results) to a big data system. For example, it should be able to feed another machine learning system. At the moment the interfaces are limited.

We have been using Centreon since either 2007 or 2008.

The stability of the architecture is very helpful because Centreon provides its own protocol. It is called BBDO, which is a binary protocol from Centreon. It's very stable. Because if you have an outage or disconnect from a remote server to your central system, it doesn't matter. The system will continue to collect all the necessary information. Once the connection is up again or reachable, the collected data from past will be automatically transferred to the central system and be calculated there. So, you don't have a gap or missing information in there. The BBDO also has the benefit that the monitoring system will keep running, even if the central machine isn't running. So, if you have different satellites or remote servers (pollers), this is a nice thing. Because once the central machine becomes available, then it synchronizes itself without any additional administration tasks to do.

Mainly, we using Centreon 2.8.28. However, we are also developing own features for the newest version 19.04. With the newer version, we want to release it for our customers and use it for them in the upcoming weeks.

Monitoring is the main topic for our team. For us, it is full-time maintenance, but this is because we are the customer's contact person. We take care of many customers, so we have to know what we are dealing with and take care of many questions all day long. 

Out-of-the-box, Centreon scales without any limits, from a default point of view. You can add different pollers to reduce the loads on another poller. From the outside, you have a web server on the internet, where you can monitor it. 

For the future, it would be great if Centeron redesigned the way of holding the performance data, especially for Monitoring Business Intelligence (MBI). This is an enterprise product of Centreon, and the amount of data stored there is not a small thing. Maybe, they could phase in with another amount each year or use Elasticsearch to reduce the data amount and query time, because the MBI module from Centreon is very nice, but the data storage is huge. This is something that they can take care of to make it a bit better. 

In general, Centreon scales great without any limits. If you have a limitation on a single poller, you just have to set up a new second, third, or fourth poller. Then, you can distribute your monitoring.

In our organization, we have around 100 people using it (out of three companies). We have 50 different customers of a wide range, like automotive and medical, who are all independent, self-standing companies.

It is very easy for one single customer to get support with Centreon.

Normally, we don't need technical support from Centreon directly. As a partner, we deal with any sort of problems ourselves daily. It doesn't matter if it is a Level 1 or 2 problem. Level 3 problems can be also solved by our own team, in most cases. Though, in one out of ten cases, we need to contact Centreon directly, and when we do, they are very helpful. 

In a worst case scenario, we need to schedule an appointment with a Webex session (remote session), but that is something that has worked really well in the past. We make an appointment with the customer together, then we can solve the problem very quickly.

Centreon does very well supporting their partners and customers. It doesn't matter if it's technical or another point of support. Their support is very good.

Previously, we used Nagios, which is the general base of Centreon. Nagios is a monitoring solution that is open source. It was one of the first monitoring tools available to the public. In the past, Centreon was just a critical interface for creating the configuration of Nagios. This changed in the last couple of years, so Centreon is now a completely self-standing product.

The initial setup is pretty straightforward, because it's very easy to get it running. However, you have to spend some time with it to get it to life, because if you just set it up, it is empty. Therefore, you have to take care that there are some holes in it, and you need to monitor some things. This is back to my point about a better API for the future as an improvement.

To get a basic view of your environment, it normally takes two to three days. However, if you want to go into detail, it depends how large your environment is: It could be hours or weeks.

We are Centreon partners, so we use our implementation strategy almost daily for our customers and ourselves. If we set it up, we ask the customer, "What are their needs?" We have a best practice, so we install the basic systems made in a network scan, which are pretty easy. If you have a scan, you can use the API to import a host. Then, you can use the monitoring really quickly.

If you have an outage in your environment, every minute counts. Every single minute that you can save with Centreon is a good reason to use it. 

We and our customers have saved so much time that we are acting instead of reacting to a situation in a positive way. You can get the investment back within a few weeks. 

If you can imagine having an outage of your infrastructure and 100 people cannot work for any reason against a small outage, which was indicated by your monitoring system and could be avoided, then this is an estimated ROI calculation.

The pricing starts at around 5000 euro. However, this depends on: 

• Your environment
• The size of your host
• How many hosts that you have.
• How many remote pollers that you have.
• If you want to use the Monitoring Business Intelligence or Centreon MAP functionalities.

You purchase a package. You have a support contract (there is also a platinum support contract) and it is per module. That means you have to pay, e.g., for the MBI module or the BAM module. Or, if you want to save a lot of money, you can pay for IMP, which is the complete package.

The pricing setup costs and licensing weren't very good in the past. The customers generally said the pricing of Centreon was fair and cheap if you compared it with other solutions. However, in the last few years, Centreon changed the license model multiple times, telling us the current model will not be stable. Many of our customers were confused about the many changes with the increasing license costs. Our customers wanted to get the support and contact person of their countries. The business investments of our customers are well planned for the next few years, not just the next two years, but this was the way Centreon thought in the past. Our customers want a stable, attractive base for investing that they can call upon. We were able to figure out a solution with Centreon for every single customer to solve this problem in the past. 

For the future, it would be nice if they have a more stable pricing model. Centreon has told us that they know about the issue, and they will try to adjust it to make it better in the future.

We have taken a look at other solutions, like Zabbix, Nagios, Check MK, and PRTG. For us, Centreon is the best solution, because we have all the benefits from the other solutions. Not all, but most of them. It's a great product to monitor our environment, so we can prevent any outage or misconfiguration on some hosts.

A main feature that sets apart Centreon versus its competitors is the possibility to expand the monitoring. You can set up different satellites to expand your monitoring or get an inside view of a special environment, such as a DMZ zone. Or, if you want to monitor a branch office from another country, so you can monitor it with an inside view of it, not just an outside view. 

We use the remote server functionality on some customer sites, because you can see an independent view and are not dependent on a single connection. If you have branch offices or bigger office outside your headquarters, you can use remote servers because if the connection is broken or disrupted, then the remote server will obtain a view of your environment and server availability. This is a good point against using other solutions. Because with other solutions, you don't have this feature. Then, you will be blind if you have this type of a situation.

Centreon is definitely not a perfect or bug-free solution on the market. On the other hand, which solution is that. They have a great support that you can count on, along with continuous improvement, which is very important for any customer when getting help in a support case.

The most part, Centreon is open source, free, and available to everyone. So, if you phone back you can submit an issue to the GitHub repository or source it directly for help to other users. If you want to set it up, you can do it easily. If you have some problems, you can also take a look at the publicly available documentation from Centreon. No matter which solution you use, you should be aware that every solution needs time to invest for a good, pure result. For Centreon, and also in other monitoring systems, you have to spend time with it because monitoring is a permanent process, which should be improved daily, but you should focus on the important things. 

We use Centreon a lot, but we could use it a bit more in the future, because Centreon is nice in a way that it is not just monitoring. You can also make the documentation of your network topology without any additional work. If you take care of your monitoring, you have automatically created a topology of your network, so now you have documentation of it. This is also a time saver.

I am splitting my rating into two parts. Centreon is an open source, available product. I would rate it with a nine (out of ten). For the license costs, I would give it a seven (out of ten) because that is something they need to improve, so the customer could better plan their investment in the future. This is information that we have received from our customers as feedback. They are really satisfied with the solution, but not 100 percent satisfied with the licensing model, even though this has been improved a little in the past. So, my overall rating is an eight (out of ten).

We basically use the solution to host monitoring for our customers. We are trying to upsell them to use some of the more advanced features of Centreon, however, unfortunately, we haven't succeeded in doing so yet.

I've only really worked with the basic features of Centreon, including the monitoring and simple reporting for dashboards. 

I have seen on the demonstration that there are a lot of other features which could be interesting, however, I have not had the chance to really see them or deploy them for our customers. 

We have the business activity monitoring, the map, and the MBI modules and they are all very good.

One of my pet peeves with Centreon is that it's not easy to determine what the end results are of all of the inheritance from the different hosts and service templates, for example. If there was a way to easily determine, for example, for a specific host, which notification settings or service settings, would be ideal to set. 

Currently, we have to go through all of the different templates and take a look at how the template is configured, and how specific parameters may change across different templates with different precedents, megatons, etc. It's a lot of work and involves trial and error. I wish they could simplify the process.

The solution needs more features on the mobile app. Currently, the mobile app cannot be used to receive notifications. It would be great if the mobile app acquired the capability to receive notifications from devices. Our customers are asking for that kind of feature.

The organization has been using Centreon for five years now. However, I only have slightly more than one year of experience with Centreon, the same as my tenure with this organization.

We do encounter bugs every so often, however, the management offers the support and can easily jump in and help us fix those issues. Overall, it's stable. We do encounter some issues simply due to the fact that no software product is perfect. That said, they are very good at quickly addressing and resolving them.

I don't have any experience with scaling. It's supposed to be scalable on paper, however, I haven't really tried it in practice nor do I know other people who have tried to scale it up. Therefore, I have no firm opinion of the potential to do so.

In general, we have about 30 users on the platform at the moment. Most of them are customers who have read-only access.

Technical support has been great at being responsive when we've dealt with bugs on the system. We're satisfied with the level of support they provide.

I can't really give an answer due to the fact that, when I came on board, we had already been using Centreon for quite some time and I have not really explored what was used before they started using Centreon in the organization.

When I came on board, Centreon was already up and running, and I did not have the experience of going through the initial setup. As it was already complete, I can't really speak to the process. I don't know if it was straightforward or complex or how long the deployment took in general.

My management has had some issues with the pricing, primarily due to the fact that we actually are currently still a Centreon partner in Asia. Unfortunately, we were not able to really capitalize on the partnership, so we are ending the partnership. 

We are moving from the expensive Centreon Enterprise edition and downgrading to the IT edition. You could infer from that there are issues with pricing, however, had we been able to successfully sell Centreon or Centreon-based services to more customers, we might have stayed on Centron Enterprise. Since it's just for a few customers, the Enterprise edition does not make sense due to the rather high pricing.

We still have a partnership agreement in Asia, however, we are mostly just a customer. Our business relationship with the company is coming to an end and we are downgrading from an Enterprise solution to an IT one.

The way the architecture of the solution is set up, the central server is on the public cloud, and for each customer, we have on-premises servers.

Overall, I would rate the solution eight out of ten.

We use it for monitoring. We have more than 20 clients and we use Centreon to monitor our clients' infrastructures. We are a service center for infrastructure monitoring.

I can't point to one valuable feature. All of Centreon is good.

There is room for improvement in the area of artificial intelligence. The product gives us a lot of information, but it's only information. We want the product to do more auto-remediation.

We've been using the solution for ten years.

It's built for the duration. It's very stable.

The scalability is intermediate. It's in some ways it's very scalable and in other ways it is not. But it is only a monitor. It's only used to get the information on the infrastructure. We don't ask for scalability. It's a very good product for the price. It does the job.

We have a close relationship with the designer of the solution. Our companies work closely. So when we have a technical difficulty with the product, we call them. They make changes and they patch and fix the product. The support we receive is good. It's very interactive. We have good communication with them. They understand the issue and they solve it very quickly.

In theory, it could take a lot of time to find a solution to an issue, but they find the solution. They have changed the product code because of issues. The solution is quite developed and Centreon as a company is very agile.

The implementation was very easy.

The competitive products have value, but we have used this one for more than ten years and we are not planning to change it.

My advice would be don't do it by yourself. While it's very easy to implement it, and it's free, contact the company and take advantage of their experience to have a perfectly designed solution. In this area of IT, the more precise you are, the better the solution. In monitoring, if you have too many options it's useless. You have to be very precise when you implement the solution. So, go with Centreon. It's more efficient than doing it by yourself.

It's not fancy, it's not glamorous, but it's a good workhorse. It's very pragmatic and it's very easy to use. It provides global information about the network and the servers. It's not the fanciest product, but it's good.

We are directly in contact with the company. We communicate with them so that we can deploy a solution with them. We share a lot of experiences between our two companies. They meet all our needs and all the features we want them to implement. We have a lot of meetings between us to change the product and to go for innovation inside Centreon. We have everything we need with the product.

I would rate the solution at nine out of ten. Ten is never possible. Products always need improvement because there are new features on the IT market. The evolution of the product can happen with AI. The key to this product is the people inside Centreon. A product is a product. It can be changed. It can evolve. But the relationship with Centreon is the most important factor.

We use Centreon to centrally monitor our entire global IT infrastructure and to alert us about impending issues.

Centreon enables us to proactively take action on issues before they even become incidents, which significantly reduces business disruptions resulting from controllable factors.

I find the product's scalability to be one of the most valuable features since it allows us to add unlimited devices for monitoring and to set up additional polling servers without additional license cost or downtime in our monitoring.

The Home view could be improved by adding customization functions that allow users to change the size of the widgets for a more uniform layout.

No issues with stability.

No issues with scalability.

Centreon technical support is only available during Central European business hours. When it comes to critical business solutions, there should be a 24/7 hotline that customers can rely on.

We switched to Centreon from our previous solution because of the flexibility it offered as an open source solution and because it allowed us to have more control over the design of our monitoring environment.

The initial setup was straightforward, as the product is available in ISO image format, ready for deployment. Centreon also has a comprehensive guide and documentation that are simple and easy to follow.

Open source solutions can be very cost effective for an organization looking for a product that can be quickly implemented, as there is no initial cost and there are no license renewal fees. However, it is important to take into consideration some of the related costs that may come along as needed, such as training, support, and product enhancements.

We have used SolarWinds Network Performance Monitor and SolarWinds Server and Application Monitor.

Centreon is like a sandbox for monitoring your systems. It allows you to customize and automate different tasks, such as the configuration of hosts for monitoring, and actions taken during an alert.

I recommend some training and deploying a lab environment instance, where administrators can fully understand how each feature integrates with the rest of the system to help avoid early configuration mistakes and achieve an efficient production environment design.

We deploy Centreon for our customers' infrastructures. They use Centreon to create alarms to be able to anticipate problems. It works for big companies and institutes. As a Centreon partner, we have different types of customers.

When we started to work with Centreon, there were about 30 people in our company and now there are 90 people, so our company has been growing and growing with Centreon. One thing that I love is that today, as a Centreon partner, we have a dedicated person who is in charge of our relationship with Centreon.

When looking at the product, for me, the best improvement is Centreon MBI. When I started with Centreon, this feature didn't exist and it's very good.

The most important feature is that it permits us to receive alarms if there is an incident within the infrastructure. 

The feature I love the most is the reporting feature, the MBI (Monitoring Business Intelligence) which permits us to send advanced reports to our customers in PDF format or in Doc format.

We also deploy Centreon Map which gives our customers intuitive views of their respective information systems.

I would like to see a better UI, one which is more responsive. This would be an improvement. Other than that, at the moment, every one of our customers is satisfied with this product.

The stability is better now. A few years ago, the product was not very stable, but it's much better now, in 2018. It has really improved. We no longer have any performance problems.

We haven't had any issues with scalability.

We have support with Centreon, so if we run into an issue, we open a ticket on the platform and they are good. We don't have any problem with them. I am satisfied. They always respond to our emails and our tickets. They are really good.

We used Nagios before Centreon. I prefer Centreon because Centreon vs Nagios provides a web interface without having to spend more on a license for it. That is why we migrated from Nagios to Centreon.

When I started with Centreon, the initial setup was very difficult because they didn't package the product. But now, setup is very easy and we are able to deploy Centreon very quickly.

As a Centreon partner, the pricing is good. We get a discount. It's a really good product so I would say the pricing is correct.

I rate Centreon at nine out of 10 because I think the user interface can be improved. That's why I don't rate it a 10. But, from my point of view, this is one of the better monitoring products.

We use it for infrastructure monitoring.

The improvement has been the ability to deploy a log monitoring system on already existing infrastructure. When I took ownership of teams where I replaced the previous monitoring solution with Centreon, the capability to stabilize and quickly fix the infrastructure monitoring - since the previous solution was not very good - helped us.

It also gives us a good overview of our system.

The collection part, due to the flexibility and scalability.

We have provided feedback to Centreon directly. The most important issue is the capability to interconnect with other systems. It already exists for some of them. For example, the Stream Connector is something we use to populate data in another system. This kind of facility for connecting should exist for all products that it makes sense to have connected to a monitoring solution.

We have never had a big issue. Sometimes there is a mistake, the wrong configuration for example. But there has been no outage caused by a bug in the software.

We haven't had any scalability issues with the monitoring solution part. But in terms of data, analysis, we have a very large amount of data, a big database. The MBI, the Monitoring Business Intelligence part is very important for that because we have limited data analysis, graphing, and reporting. With the new solution, we will have success with that. This improvement will enable a lot of functionality and features in terms of Big Data treatment.

We have direct contact with a pre-sales engineer. We work directly with him by email or by phone, it's very fast. I don't use the support gateway from Centreon.

We had a different monitoring system. Why Centreon? It's very good at agents, in collecting data. Because of some specific integrations we must do, we chose Centreon. Based on demand and our expectations, and the collectors, we made our decision.

We picked Centreon because, after an open-source comparison, and given what we want to do, and our skills and experience as well, it was the best solution for us, the most reliable for our services. We manage the unified collaboration clusters for an organization in Europe. The difficulty is that we have to maintain a complex solution so I don't want to increase the complexity of managing it. The opposite would be the best way, to effectively simplify the management of this kind of cluster. Centreon is made for monitoring but also has extra connectors to enable automation. Globally, that was a very important point for us, to open the door to tomorrow. If we stay with Centreon, we should be able to play with the data, with Centreon and with other systems.

The first setup was eight years ago and it was not very complex. We had an expert in Linux so it was not really a big issue, with ten years' experience in monitoring systems. There were no specific difficulties with it.

We have a good monitoring system and a good aggregation layer. That means we are alerted on service impacts and not when something is down. We have saved a lot of time on non-business-hours intervention.

I deal with technical parts, not with the costs.

In terms of licensing, the big question will be the ability to be flexible with the scale of design.

We had different solutions. We had Splunk for Big Data monitoring as well as Elasticsearch and Zabbix. These are at the top of the market, along with Centreon.

My advice is to make it simple. When I say that, it's in terms of templating. With Centreon we can create a lot of templates. It is very good to have something very flexible and configurable. But be careful, don't create a lot of templates that will clash with other templates because, in the end, it will be very complex to maintain. Start simple and maintain up-to-date documentation.

We use other reporting solutions to complement it, to create beautiful reports that are specifically requested by our customers. In the future, I expect we will use a diverse range of products to give us the value we need to present to our customers.

I'm a solution architect, so my main job is to provide good solutions to meet demands. When we build a design, we study which solution will make sense for the customer. As an integrator, of course, I need to be sure that any solution, for the price, will make sense for my enterprise as well.

If we compare Centreon to another open-source monitoring system, and we're talking about it as a pure monitoring system, I would rate Centreon between eight and nine out of ten. If we compare it to a Big Data system, it would be closer to seven out of ten, due to the Big Data capacity that we don't have with Centreon. Strictly on monitoring, it gets a good score but with the new technologies, what we see with Big Data and the capabilities for machine-learning and AI, etc., the latter will have a better score because they have the capability to generate a lot of metrics.

We use Centreon for monitoring resources to prevent priority-one and priority-two tickets. It is our primary monitoring tool. All our devices are being monitored using Centreon.

We have reduced the number of priority-one and priority-two tickets by about ten percent.

What I like most about Centreon is that it is very flexible and customizable, based on the user and/or business needs. Centreon is very flexible when it comes to monitoring parameters. We can use scripts found on the internet or scripts created by our infra/apps team.

Also, the data visualization features are very simple and straightforward, yet very informative.

Finally, it is very simple and user-friendly. It is easy to understand and to make your way around it.

Centreon needs to improve the granularity of the data as well as the graphical data. It would also be better to if there was improvement to the filtering/grouping system as well as the creation of views.

It would be a lot better if they improved the scalability and granularity of the data.

Technical support is great, very helpful and accommodating.

We had a previous solution. We switched because we are trying to save some money and, at the same time, looking for a solution that will support our business needs. This solution was suggested by upper management.

The initial setup was very simple and straightforward, including installation, adding of nodes, creating services, etc.

The solution is very effective, despite the low price.

Follow the best practices and the installation process in the documentation. It is very easy to understand.

In terms of the Remote Server functionality, I'm not highly familiar with it yet, but based on what I have read I think it is a great feature and I'm open to any possibility of using it in the future.

We have 300 to 400 users. Some are infrastructure engineers, VPs, application analysts, and people on the upper management team. For deployment and maintenance, we have three to five personnel: our Senior Vice President, Linux/VM engineers, and global operations engineers.