Centreon Shifts into Observability with the Acquisition of Quanta.io
Learn more about the Centreon platform.
Be informed of the latest product updates.
The top 3 reasons to register to The Watch.
Hello team,I have a LDAP configured with an Active Directory. It works fine but when I move a user to an other OU, they can no longer log in to Centreon.If I delete the user from Centreon and then they log in again, the authentication works.Do you have any idea what might be causing this behavior?
Suite à la migration de ma plateforme Centreon depuis la version 21.10 vers la version 24.10 sous Debian, j’ai constaté un dysfonctionnement concernant l’affichage des hôtes dans l’interface Web.Les hôtes sont bien présents dans la base de données et ont été ajoutés avec succès. La génération de la configuration été effectuée sans erreur j’ai ajouter un hote mais n’est pas afficher dans status des ressources
Hi,I have an issue with this command :/usr/lib64/nagios/plugins/centreon_plugins.pl --plugin cloud::azure::management::monitor::plugin \--custommode='api' \--mode='get-metrics' \--subscription=xxx \--tenant=xxx \--client-id=xxx \--client-secret=xxx \--resource=xxx \--resource-group=xxx \--resource-namespace=microsoft.insights/components \--resource-type= \--metric=requests/failed \--aggregation=Count \--interval=PT30M \--filter-dimension="request/resultCode sw '42'" \--warning-metric=1 --critical-metric=5When there are no hits, i get:UNKNOWN: No metric found (Are the filters properly set?)Can't find any option to get OK instead of UNKNOWN when the filter is empty.
Hi all,We use here Redhat 8.10.Our policy is not to create local users on our linux systems.Instead all our users are in Active Directory (with linux attributes).We use Centrify to map the Ad users to the local linux system (https://delinea.com/centrify)This is why all our centron users are not present in /etc/passwd (centreon, centreon-broker, centreon-engine, centreon-gorgone)But they do exists and can be used as usual to start process, as owner of files ...etc → All our Centreon Platform is running well with this Centrify configuration ….BUT we are facing an issue while upgrading :EX: during “dnf upgrade centreon-common.noarch”The rpm scriplet provided by centreon runs this : if getent passwd centreon-broker > /dev/null 2>&1; then usermod -a -G centreon-broker centreon usermod -a -G centreon centreon-brokerfiBut it fails with : Running scriptlet: centreon-common-23.10.11-1.el8.noarch 7/138usermod: user 'centreon' does not exist usermod: user 'centreon-broker' does not
Hello, i’m wondering if i missconfigured a centreon. It is based at Mexico city and by so is configured on the America/Mexico_City timezone.I’m working on the version 23.10 of Centreon.This timezone is setup in the PHP configuration, in the global configuration of the instance, and configured as the timezone of the user.As i watch the graphs of my services in the resource tab, i see the data at the proper times but when i look into legacy screens or through custom views, the data is an hour late.Maybe i missed a configuration somewhere ? but it seems it’s only on that timezone. I read online that Mexico removed their summer time shift, so maybe it is related.Has anyone faced this kind of issue ?
Good morning, I want to ask how to add in Centreon (with license) a Lantronix SLC device that have 2 interfaces with 2 IP.The connection of the devices is as follows:Eth0 → Firewall 1 (active) Eth1 → Firewall 2 (standby)When Firewall 1 is active, the device is reachable via IP of Eth0 and the IP on Eth1 remain unreachable.We use SNMPv3 and Centreon enabled for active checks.When we switch traffic on Firewall 2, we reach IP of Eth1 and lost reachability of IP on Eth0.If I add both IP as single device, it’s all ok, but I would like to group the two IPs into a single object.Is it possible to do that? If yes, what is the process to do that?Thanks a lot for your support, let me know if you need more informations.
When IWhen I connect to custom view in saml, the page is redirected to the authentication page. Have you ever encountered this problem? On the other pages this is not the case.
Hi I have had a problem with centreon updates for some time. My version is 24.10.8. The problem is in the vmware infrastructure monitoring plugin. Previously (based on the centreon_vmware.pm file) everything worked fine. After updates (from several versions within 24.10) the centreon_vmware service does not want to start. When I change the option to old in the /etc/default/centreon_vmware file and restore the centreon_vmware.pm file, everything returns to normal.Here is the configuration and logs after updates (the last one to 24.10.8), which do not work well.My instance: Centreon 24.10.8, Debian 12. $ ls -lrazem 44-rw-rw---- 1 www-data www-data 1287 2018-10-17 centreon.conf.php-rw-r----- 1 centreon centreon 390 06-24 08:25 centreontrapd.pm-rw-rw-r-- 1 centreon centreon 390 2024-05-16 centreontrapd.pm.dpkg-dist-rw-rw---- 1 centreon-gorgone centreon 626 06-24 08:24 centreon_vmware.json-rw-r--r-- 1 centreon centreon 812 03-28 09:37 centreon_vmware.pm
Hey everyone, I’m currently following the documented steps to set up NRPE monitoring for Windows hosts with Centreon. https://docs.centreon.com/pp/integrations/plugin-packs/procedures/operatingsystems-windows-nsclient-05-nrpe/Here is what has been completed so far : Steps already done:Installed the NRPE plugin on each poller:yum install centreon-nrpe3-pluginInstalled the Windows NRPE 0.5 Centreon Pack on the Central server:yum install centreon-pack-operatingsystems-windows-nsclient-05-nrpe Issue encountered :In the Centreon Web interface, underConfiguration > Connectors > Monitoring Connectors,the "Windows NRPE 0.5" Monitoring Connector does not appear as installed. When I try to click on it and use the “Subscribe” button, I am redirected to the Centreon Store,but the store is currently unavailable and displays the message:“The Store is getting a makeover”As a result, I am unable to install the Monitoring Connector and complete the configuration. Questions:Is the Windows NRPE 0.5
Hi everyone,I installed a poller on a Raspberry Pi 4. The Centreon central server is hosted on a VM (so they are not on the same local network).After creating the poller, I ran the following command:bash /usr/share/centreon/bin/registerServerTopology.sh -u <API_USER> -t poller -h <CENTRAL_IP> -n <POLLER_NAME> The poller appears in the Centreon interface. I selected it, copied the configuration provided by the interface, applied it to the Raspberry Pi, then restarted Gorgone on both sides. I also exported the configuration from Centreon.But the poller still doesn't run.In the Gorgone logs, I see the following message:ERROR - [proxy] Send message problem for '8':Do you think this could be the issue?Thanks in advance for any help.
Hi,We recently upgraded our centreon infra from 24.04.12 to 24.10.7.Our mariadb server (On a standalone redhat serveur) is version 10.11.10 Just after the upgrade we noticed that the CPU_LOAD on the database serveur is increasing pemanently and regulary … Now 100% CPU is reached … an the top report : load average: 11.56, 9.75, 9.59(Usually it is below 1,5)We have 4vcpu on the redhat server.After enabling the lonq_query logging I noticed that I have between 1 an 14 similar requests running in PARALLEL :SELECT contact.*, cp.password AS contact_passwd, t.topology_url,t.topology_url_opt, t.is_react, t.topology_id, tz.timezone_name, t.topology_page as default_pageFROM `centreon`.contactLEFT JOIN `centreon`.contact as template ON contact.contact_template_id = template.contact_idLEFT JOIN `centreon`.contact_password cp ON cp.contact_id = contact.contact_idLEFT JOIN `centreon`.timezone tz ON tz.timezone_id = contact.contact_locationLEFT JOIN `centreon`.topology t ON t.topology_page
I am encountering persistent authentication issues while trying to access the REST API of a Dell ME4012 storage system. Despite providing valid credentials and testing multiple configurations, the REST API consistently returns an Authentication Unsuccessful error.Steps to ReproduceAttempt to log in to the Dell ME4012 REST API using curl:curl -k -X POST https://192.168.1.3/api/login \ -H "Content-Type: application/json" \ -d '{"username": "Admin", "password": "Password"}'Observe the following response:<RESPONSE VERSION="L100"> <OBJECT basetype="status" name="status" oid="1"> <PROPERTY name="response" type="string" display-name="Response">Invalid sessionkey</PROPERTY> </OBJECT></RESPONSE>Attempted the same with both controllers (192.168.1.3 and 192.168.1.4), but the same error occurs.Repeated the test with:HTTP Basic AuthenticationBoth curl and the centreon_dell_me4_restapi.pl pluginNo changes in the outcome.Expected BehaviorAuthentication shoul
If you have any ideas for features that you think will help us further improve Centreon, share them with us now!
All you need to start or enhance your Centreon journey.
If you are a customer, contact our support team and we'll be happy to help you.
A library covering a range of relevant topics in a variety of formats.
Join us in nurturing the Centreon open source project.
A rich collection of webinars and other insights on the Centreon universe.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.