Skip to main content

    Filter by idea status

    Filter by product

    653 Ideas

    Horst KitschSteward ***

    check period and notification period are dealing with time periods, but recurring downtime does notNeeds Votes

    We are facing the following situation:Our company has hundreds of retail sites around the world. We’re doing network monitoring for those sites. Many of these sites do NOT have power during the night and therefor they are not reachable.Of course, we don’t want to have notifications during that period or tickets for a known recurring situation!We started with notification period settings to send notifications only during the time, when the retail stores should be open. That works fine, BUT during downtime, they still appear as critical and/or unknown in the resource monitor. This makes the resource monitor less useful for other services we should care about.Using check period instead would keep the resource monitor ‘clean’ and prevent from unnecessary notifications, but we’re ‘blind’ during night time. Reporting might be difficult (not completely thought about) and we like to have as much insight as possible, but check period will stop polling.Now we came to recurring downtimes! I think, this would exactly do, what we expect - continue polling and visibility of the status 24x7, but treating occuring events as ‘handled’. No notification, no ticket and a clean resource monitor.All good so far, but the recurring downtime is terrible to configure, if you need a downtime every night with different start- and endtimes, you need a weelky ‘plan’ with 14 periods - i.e. Monday, midnight until 10 AM and 8 PM until midnight and this for every day of the week.Wouldn’t it be good to use the time-periods also for the recurring downtimes as already for check and notification period available?A long explanation for a simple topic.

    Make centreon compatible with linux centrify users - For UpgradesIn Backlog

    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 exist usermod: user 'centreon' does not exist usermod: user 'centreon-engine' does not exist error: %prein(centreon-common-23.10.11-1.el8.noarch) scriptlet failed, exit status 6This is because ‘usermod’ need real linux local users (present in /etc/password)So the package is not installed … and other foloowing commands (chown /  chmod) in the scriptlet are not executed at all….Would it be possible not to exit when these ‘usermod’ are failing ??This could be possible with the || true option for the usermod commands :usermod -a -G centreon-broker centreon || true Thanks 

    Lenteur d'affichage des downtimes - index manquant - LIKE '%%'Released

    Bonjour,En prestation pour un client grand compte, je constate des lenteurs d’afficage lors de l'appel à la page downtimes  /centreon/main.php?p=21001il se passe une bonne quinzaine de secondes, au  minimum, avant que les données apparaissent.En recoupant avec un Expert DBA de mon client grand compte, il s'avère que la requête SQL de l'affichage des downtime ne semble pas optimale. La partie des filtres, notamment, ne sont pas correctement indexés (host, acteur, descriptions...)De même, si les champs de recherche sont vides, il n'est pas nécessaire de mettre LIKE '%%'. la requete en question : (SELECT SQL_CALC_FOUND_ROWS DISTINCT 1 AS REALTIME, d.internal_id as internal_downtime_id, d.entry_time, duration,        d.author as author_name, d.comment_data, d.fixed as is_fixed, d.start_time as scheduled_start_time,        d.end_time as scheduled_end_time, d.started as was_started, d.host_id, d.service_id, h.name as host_name,        s.description as service_description  FROM downtimes d, services s, hosts h WHERE d.host_id = s.host_id AND d.service_id = s.service_id AND s.host_id = h.host_id AND d.type = 1  AND d.cancelled = 0 AND s.description LIKE '%%' AND h.name LIKE '%%' AND d.comment_data LIKE '%%' AND d.end_time > '1732196593'  AND d.comment_data NOT LIKE '%Downtime cycle%'  AND d.author LIKE '%%') UNION (SELECT DISTINCT 1 AS REALTIME, d.internal_id as internal_downtime_id, d.entry_time, duration,  d.author as author_name, d.comment_data, d.fixed as is_fixed, d.start_time as scheduled_start_time,  d.end_time as scheduled_end_time, d.started as was_started, d.host_id, d.service_id, h.name as host_name,   '' as service_description FROM downtimes d, hosts h  WHERE d.host_id = h.host_id AND d.type = 2  AND d.cancelled = 0 AND h.name LIKE '%%' AND d.comment_data LIKE '%%' AND d.end_time > '1732196593'  AND d.comment_data NOT LIKE '%Downtime cycle%'  AND d.author LIKE '%%') ORDER BY scheduled_start_time DESC LIMIT 0, 50Pourriez-vous prendre en compte ces remarques pour vos futurs releases ?Cordialement Emanuel BourelADN-Consultingticket de support associé : https://support.centreon.com/hc/fr/requests/79841