Try our new research platform with insights from 80,000+ expert users

Centreon vs InfluxDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Centreon
Ranking in Network Monitoring Software
20th
Ranking in IT Infrastructure Monitoring
17th
Average Rating
8.4
Reviews Sentiment
7.2
Number of Reviews
31
Ranking in other categories
Cloud Monitoring Software (16th)
InfluxDB
Ranking in Network Monitoring Software
52nd
Ranking in IT Infrastructure Monitoring
45th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
10
Ranking in other categories
Non-Relational Databases (3rd), Open Source Databases (12th), NoSQL Databases (5th)
 

Mindshare comparison

As of May 2025, in the Network Monitoring Software category, the mindshare of Centreon is 2.5%, down from 3.1% compared to the previous year. The mindshare of InfluxDB is 0.3%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software
 

Featured Reviews

Caulson Chua - PeerSpot reviewer
With fewer staff resources, we can identify and address issues before the system goes down
Centreon's most valuable features are preventative maintenance and cost-efficiency. Everything is monitored, and we get a log before the system fails. We have an opportunity to fix the issue and avoid downtime. The dashboard is user-friendly, and the solution provides good reporting and visibility. The layout is straightforward. You can click on the drop-down list to select the server you want. The anomaly detection feature helped us reduce our average resolution time by 30 minutes to an hour.
PedroCampos - PeerSpot reviewer
A powerful, lightweight time series database with a simple query language and easy setup
Influx has TICK Stack, which contains multiple services and multiple products that work together. InfluxDB is just a time series database, and it works really well. I haven't yet had the time to look into the new stack based on Influx 2.0, but currently, as a time series database, InfluxDB is working the way it is supposed to work. In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version. I would also like to have high availability features, such as replication, active-active, etc. If they can put an extra plugin or service on top of it, it would be something interesting. I am not sure if they have high availability to make it data center-aware for clustering. For example, I am not sure whether you can have it at different locations with big clusters that are location-aware. Even in their documentation or presentation, they talk too little about high availability and extended clusters with different locations. They might already have it in the newer versions. We have Influx 1.8 in our production in the stage and internal workloads environments. The other products in their ecosystem, such as Chronograf, can be improved. Chronograf is a dashboarding or visualization layer product, and that, for sure, can be improved.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We are alerted on service impacts and not when something is down. We have saved a lot of time on non-business-hours intervention."
"You can concentrate and orchestrate several other solutions from other vendors. You can consolidate those solutions all in one place, then maintain and monitor from that single point. This creates ease of use. It is a very powerful solution from this point of view."
"The downtimes feature is helpful. If the ISP is doing some maintenance on its network, we have the option to put downtime on the devices or the services, so we won't get any false alarms."
"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."
"We have the business activity monitoring, the map, and the MBI modules and they are all very good."
"Centreon's most valuable features are preventative maintenance and cost-efficiency. Everything is monitored, and we get a log before the system fails. We have an opportunity to fix the issue and avoid downtime."
"I can't point to one valuable feature. All of Centreon is good."
"We have a single GUI where we can view the status of all our infrastructure."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"The solution is very powerful."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
"The user interface is well-designed and easy to use. It provides a clear overview of the data, making it simple to understand the information at hand."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
 

Cons

"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."
"To get it started is a lot of work, since it comes empty. We had to push information into it to make it work."
"I went through a few things with them to do with Centreon MAP, to do with active polygons, being able to draw an area and make that active. The functionality was in the older version of Centreon MAP and in the new version, which was a complete rewrite, they dropped it."
"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."
"The product collects the information, but it fails to send them via SMS, WhatsApp or Telegram."
"Release management and quality of testing need improvement, because with each major upgrade we have many issues coming in. Then, it takes several minor upgrades to get rid of them."
"Opening a ticket on the website of Centreon can be difficult for my colleague, but not for me because my English is good. However, my colleague doesn't speak English well, as our company is in Quebec and our first language is French."
"I would 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 to a big data system. For example, it should be able to teach machine learning."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"The solution's UI can be more user-friendly."
"The solution doesn't have much of a user interface."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
 

Pricing and Cost Advice

"For more complex tasks, we use prepaid support days and ask Centreon to come onsite."
"The pricing works out well for us, given our environment and where we are."
"The price is not too high. Licensing is driven by how many hosts you monitor, but because you can run the agentless version, you don't have to declare every host to Centreon, one at a time. That means you can drive your infrastructure supervision with a very low number of declared hosts."
"Centreon is better than Nagios XI in regards to cost and support response times, when you have a problem. If you have a problem, it costs money to contact the Nagios XI support."
"It is perfect and very cheap if you are a little company or startup. After that, it is quite expensive for a big company."
"The solution has a free part and after that threshold, you will need to pay. For example, if you believe you can create an interesting map, most of the time, you will have to pay 10,000 Euros per year for having access to these components."
"Open-source solutions like this can be very cost effective for an organization looking for a product that they can quickly implement, 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."
"In terms of licensing, you have to think through if the components that need licensing are really needed. For example, the Map module: If you don't need a map to be shown, I don't see a point in paying for those licenses, if you just use it a couple of times a month or a couple of times a week... You can use the Centreon free version and get the main features. The licensing part is, I would say, only for bigger customers who have the option to pay more and who really need those kinds of modules, fancy reports, etc."
"We are using the open-source version of InfluxDB."
"InfluxDB recently increased its price. It is very expensive now."
"InfluxDB is open-source, but there are additional costs for scaling."
"The tool is an open-source product."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
11%
Government
10%
Comms Service Provider
7%
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
10%
Comms Service Provider
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Centreon?
Centreon's most valuable features are preventative maintenance and cost-efficiency. Everything is monitored, and we get a log before the system fails. We have an opportunity to fix the issue and av...
What needs improvement with Centreon?
I have certain concerns with Centreon, such as being unable to set downtime for multiple devices at once due to the limitation of adding only 50 devices in a single go. Increasing this limit would ...
What do you like most about InfluxDB?
InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data ...
What needs improvement with InfluxDB?
InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data coll...
What is your primary use case for InfluxDB?
I use the solution to store and manage data from various sensors in a production environment. I have developed a system where data from these sensors is communicated through an OPC UA receiver and ...
 

Comparisons

 

Overview

 

Sample Customers

Airbus, Bollore, BT, Canal Plus, Kuehne Nagel, Limagrain, LVMH, Oberthur Technologies, Orange, Darty, Addax Petroleum, Plastic Omnium, Auchan, Valeo, Saint Gobin, Clarins, Hugo Boss, JC Decaux, French Government (Defense, Justice, Environment, Agriculture), OptiComm, Thales, Zeiss.
ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Find out what your peers are saying about Centreon vs. InfluxDB and other solutions. Updated: May 2025.
851,604 professionals have used our research since 2012.