Network engineer at DIRECTION GÉNÉRALE DES IMPÔTS - DGI
Real User
Top 5
2024-08-20T10:04:35Z
Aug 20, 2024
I use the solution in my company for our supervision purposes. In my company, we supervise all of the infrastructure with the tool. It is a monitoring tool.
We're a software solutions provider using Centreon to monitor a client's database, application, and web servers. The system sends an email alert when something goes wrong. Currently, we only have one customer using Centreon. Our client is a global automobile manufacturer headquartered in Europe. Our customer was already using Centreon when we started working with them. They approached us about upgrading and perfecting their system. We've also pitched this solution to another car manufacturer based in Germany.
Express Manager at a transportation company with 10,001+ employees
Real User
2022-10-24T06:06:00Z
Oct 24, 2022
We use Centreon to monitor the server and network devices. It also provides reporting that informs our capacity planning with regard to storage on the server disk. We use it on-premises. We have a central server and around 14 monitoring pollers on the remote side that report to the main server. I'm the monitoring administrator, so I set up some dashboards for my colleagues and users in the IT department that are customized to provide the information they want to see. They want to look at network devices and create a map of the equipment that allows them to see usage and if something has broken down.
System engineer at a financial services firm with 51-200 employees
Real User
2022-06-20T19:10:00Z
Jun 20, 2022
Firstly, it was used to start monitoring the desktop computers of the company and all of the servers, systems, and desktop applications. Secondly, it was used for monitoring the company's network. Lastly, it was used to monitor the company's applications.
We have multiple instances with Centreon: a central, remote, MBI, report server, and two pollers. We also have Centreon MAP. All the pollers are pulling all the endpoints, sending information to the central and remote instances. If we need to produce some reports to connect, then we connect directly to the report server. If we need to produce MAPs, then we connect to the MAP server. We monitor bandwidths of all the links inside the data center as well as outside Internet links and MPLS links to have the connectivity, status, and bandwidth consumption. We have defined the threshold on these links to understand if they are being overused or not. This is the main feature. We use the same for network devices to see basic information, like a device's uptime to know if it is up or down. It is also the same for all the ports and environment probes on the hardware. For the server, we configure specific probes to check some specific services. For example, the server provides a service through a Docker container, then we can configure a specific query to check the Docker container stages. Or, if we need to have the temperature of the air conditioning system, then we configure a specific query to ask for it. So, there is basic information coming from the network devices related to hardware. There is also some specific monitoring about services that we are using in terms of the business or infrastructure on specific devices. We have 500 hosts and 4,000 services.
We are a provider of the Centreon solution and a reseller as well. We also use it internally to monitor our offices around the world. We also have a NOC for our customers hosted in Azure and AWS. We provide Centreon EMS as a SaaS solution to monitor the infrastructure (or applications) of our customers. As a reseller/integrator of Centreon, we deploy it on premise for our customers as well.
We use it primarily for monitoring our devices. We also use it for discovery. For example, if a server is down, the first step to take is just go to Centreon and have a look. I installed this solution on my company's local server. It is on the LAN network. There is a plugin for Centreon for connecting and providing visibility to the host.
CEO at a tech services company with 11-50 employees
MSP
2020-12-17T09:13:00Z
Dec 17, 2020
We use Centreon primarily for network monitoring. We monitor our customers' networks, including the internet connection and the switches, for temperature and general hardware status. For some of our larger customers, we use it to monitor servers as well, using the simple network management protocol (SNMP).
Network Project Manager at a tech services company with 11-50 employees
Real User
2020-12-02T10:27:52Z
Dec 2, 2020
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.
We are an IT company. We are using Centreon to deliver services to some of our customers. The main use is for IT monitoring of their infrastructures, especially right now in the media and telecom sectors. In the last month, we have also been approaching the public media sector in Italy.
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.
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.
Senior Networking Consultant at S & L NETZWERKTECHNIK GMBH
Consultant
2019-06-16T07:23:00Z
Jun 16, 2019
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.
Global Operations Center Engineer at a logistics company with 1,001-5,000 employees
Real User
2018-11-15T10:12:00Z
Nov 15, 2018
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.
Project Manager, Cloud Services with 501-1,000 employees
Real User
2018-11-12T09:12:00Z
Nov 12, 2018
We have our own private data centers that are set around the world. They post our solutions to our customers. We have a NOC that monitors the applications and services of each server. The primary use is of the solution is to trigger incidents and to resolve issues before the customer notices.
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.
Within our technological infrastructure and Communications Management service, it is vital to use this tool to determine the status of each managed element in a simple way.
Operation Team Engineering with 1,001-5,000 employees
Real User
2018-06-28T06:31:00Z
Jun 28, 2018
Our primary purpose for Centreon is monitoring. We use it to view the status of all our pollers, manage them, and configure them. We manage around 30 Centreon pollers. Our team is operating multiple security services (digital signatures, 2FA, secure storage, etc.). We are taking care of everything (hardware, network, hypervisors, VMs, OS, applications, security patches, backup, etc.). Centreon is used to monitor the health of each component and alert us in case of failure. It gives us an overview of our infrastructure health and provides real-time feedback when doing changes.
The primary use case is for a central monitoring system for all our IT equipment. We can predict problems and react before we have an issue on our infrastructure. We managed to merge all our technical monitoring into a single console, therefore building good availability reporting all around.
We monitor all our technical infrastructure and tickets in the ITSM tool. We have all our tickets inside Centreon in real-time and can monitor a lot of ELP and CLN in real-time for application purposes.
We have a lot of customers, we manage their LANs, firewalls, and other devices - mainly network devices - and we also monitor them. If we get an alarm we can see right away what is going on and log in to those devices to check what is going on.
Centreon is an all-in-one IT monitoring solution that is a network, system, applicative supervision, and monitoring tool. It is free and open source, and one of the most flexible and powerful monitoring softwares on the market.
Centreon Features
Centreon has many valuable key features. Some of the most useful ones include:
Supervision of hybrid infrastructures, from one end to the other
Open and flexible architecture
Open-source solution, downloadable for free
Filtering capability in...
I use the solution in my company for our supervision purposes. In my company, we supervise all of the infrastructure with the tool. It is a monitoring tool.
Centreon is a client application. We use the solution to monitor network infrastructure. In case of an incident, We can fix the issue.
We're a software solutions provider using Centreon to monitor a client's database, application, and web servers. The system sends an email alert when something goes wrong. Currently, we only have one customer using Centreon. Our client is a global automobile manufacturer headquartered in Europe. Our customer was already using Centreon when we started working with them. They approached us about upgrading and perfecting their system. We've also pitched this solution to another car manufacturer based in Germany.
We're a telecom group and we use Centreon to monitor all our services.
We use Centreon to monitor the server and network devices. It also provides reporting that informs our capacity planning with regard to storage on the server disk. We use it on-premises. We have a central server and around 14 monitoring pollers on the remote side that report to the main server. I'm the monitoring administrator, so I set up some dashboards for my colleagues and users in the IT department that are customized to provide the information they want to see. They want to look at network devices and create a map of the equipment that allows them to see usage and if something has broken down.
We use it for monitoring our software for illegal components. We look to Centreon to provide a visual representation of the availability of a service.
Firstly, it was used to start monitoring the desktop computers of the company and all of the servers, systems, and desktop applications. Secondly, it was used for monitoring the company's network. Lastly, it was used to monitor the company's applications.
We have multiple instances with Centreon: a central, remote, MBI, report server, and two pollers. We also have Centreon MAP. All the pollers are pulling all the endpoints, sending information to the central and remote instances. If we need to produce some reports to connect, then we connect directly to the report server. If we need to produce MAPs, then we connect to the MAP server. We monitor bandwidths of all the links inside the data center as well as outside Internet links and MPLS links to have the connectivity, status, and bandwidth consumption. We have defined the threshold on these links to understand if they are being overused or not. This is the main feature. We use the same for network devices to see basic information, like a device's uptime to know if it is up or down. It is also the same for all the ports and environment probes on the hardware. For the server, we configure specific probes to check some specific services. For example, the server provides a service through a Docker container, then we can configure a specific query to check the Docker container stages. Or, if we need to have the temperature of the air conditioning system, then we configure a specific query to ask for it. So, there is basic information coming from the network devices related to hardware. There is also some specific monitoring about services that we are using in terms of the business or infrastructure on specific devices. We have 500 hosts and 4,000 services.
We are a provider of the Centreon solution and a reseller as well. We also use it internally to monitor our offices around the world. We also have a NOC for our customers hosted in Azure and AWS. We provide Centreon EMS as a SaaS solution to monitor the infrastructure (or applications) of our customers. As a reseller/integrator of Centreon, we deploy it on premise for our customers as well.
We use it primarily for monitoring our devices. We also use it for discovery. For example, if a server is down, the first step to take is just go to Centreon and have a look. I installed this solution on my company's local server. It is on the LAN network. There is a plugin for Centreon for connecting and providing visibility to the host.
We use Centreon primarily for network monitoring. We monitor our customers' networks, including the internet connection and the switches, for temperature and general hardware status. For some of our larger customers, we use it to monitor servers as well, using the simple network management protocol (SNMP).
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.
We are an IT company. We are using Centreon to deliver services to some of our customers. The main use is for IT monitoring of their infrastructures, especially right now in the media and telecom sectors. In the last month, we have also been approaching the public media sector in Italy.
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.
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.
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.
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 our own private data centers that are set around the world. They post our solutions to our customers. We have a NOC that monitors the applications and services of each server. The primary use is of the solution is to trigger incidents and to resolve issues before the customer notices.
We use it for infrastructure monitoring.
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.
Within our technological infrastructure and Communications Management service, it is vital to use this tool to determine the status of each managed element in a simple way.
Our primary purpose for Centreon is monitoring. We use it to view the status of all our pollers, manage them, and configure them. We manage around 30 Centreon pollers. Our team is operating multiple security services (digital signatures, 2FA, secure storage, etc.). We are taking care of everything (hardware, network, hypervisors, VMs, OS, applications, security patches, backup, etc.). Centreon is used to monitor the health of each component and alert us in case of failure. It gives us an overview of our infrastructure health and provides real-time feedback when doing changes.
Monitoring our telecommunications network.
The primary use case is for a central monitoring system for all our IT equipment. We can predict problems and react before we have an issue on our infrastructure. We managed to merge all our technical monitoring into a single console, therefore building good availability reporting all around.
We monitor all our technical infrastructure and tickets in the ITSM tool. We have all our tickets inside Centreon in real-time and can monitor a lot of ELP and CLN in real-time for application purposes.
We have a lot of customers, we manage their LANs, firewalls, and other devices - mainly network devices - and we also monitor them. If we get an alarm we can see right away what is going on and log in to those devices to check what is going on.
We use Centreon to centrally monitor our entire global IT infrastructure and to alert us about impending issues.