Recently active topics

Veeam has released version 13, which is no longer compatible with the current Centreon connectors.In this version, access is only available through the REST API:https://helpcenter.veeam.com/references/vbr/13/rest/1.3-rev0/tag/LoginVeeam is now provided as a Linux appliance with specific command sets.Could you please consider updating the Centreon plugin to support this new version and its REST API access?

Rubrik 9.4+ now moves many on‑prem clusters to RSC‑only management, disabling local CDM REST APIs. As a result, the current Centreon Rubrik REST API plugin cannot monitor these environments, since it only supports CDM clusters and not the RSC console.Rubrik officially transitioned from REST to GraphQL APIs for RSC management and recommends using GraphQL for monitoring.A GitHub issue already requests GraphQL support for the Centreon plugin, but no RSC‑compatible plugin exists yet.Request:Please add an official Centreon Plugin Pack supporting Rubrik Security Cloud (RSC) using GraphQL and RSC authentication (client_id / client_secret).Thank you!

Right now when a use is on Centreon and wants to create a host, the only component they can use to decide what to implement is the Template select field.This is a little bit raw to let users discover what they want to install.In a similar way as Connectors or the new wizard for pollers, i would like to be able to let users go in a cleaner interface to choose what template they are looking to implement.This could take many forms as it’s more related to how the UI would show the information to the user and i’m unsure how easily we can structure this from the list of templates.But this is my idea, to avoid the hassle of the user going through documentation to find what host template to use, to prefer to stay on the centreon and go through a wizard to choose what template to integrate. What does the community think of this ?

Hi, We want an upgrade for endpoint “broker/graphite” and add some variable like hostgroup for dissociate datasource on grafana by application. Its a security imrovement for us. We want add MIN and MAX for more simplicty on our grafana too. thank you.

Hi,it should be great to have a specific check method that do only one check by day, at a random hour.For now, we can do a 1 check service on a specific time period, but all checks are done at the start of the time period.When we need only one check by day for a service, we don’t care about the time of the check, and it will be more light to process for pollers.

Bonjour,Les dashboards de pilotage sont dans l’air du temps et avoir d’autres styles de graphe sur centreon serait top : Exemple : Bulles de dispersion : Graphes de points : Camembert  : Cordialement,

Hello Centreon,I would like to write long texts or texts with multiple lines in a MAP.But the text object does not currently allow this.It seems there's a very short limit or something preventing line return.To create a long text, I must to write each line in a separate object, which is not really suitable. Thanks and best regards 

Hello,Would it be possible to get the state type (SOFT/HARD) from the timelines retrieved by API ?For the endpoint : /monitoring/hosts/{host_id}/services/{service_id}/timelineWe would like to get the field "state_type". It is present in /monitoring/services endpoint.When a service gets critical, we have every tries in the timeline (also in the web interface). Having the state type would allow us sort each event in the timeline.

Hello,In the availability section, it is possible to filter by period but not on the dashboard which I find unfortunate.The idea would be to allow within the status chart the ability to define a time period just like in the availability section. This would make it possible from the dashboard to view host statuses over for example the last 7 days, the last hour, or even the last month, etc...Have a great day everyone!

 referenced tohttps://github.com/centreon/centreon-plugins/issues/6117 I can add more information if required in github issue

Hello!!After contacting support to inquire about the roadmap for VMware 8 connectors, they advised us to post our requirements on The Watch, so here goes: Persona : For everyone Problem to solve : Ensure that the same checks are performed as with connector 7 when switching to connector 8 Expected outcome : ESX-HEALTH, ESX-ALARMS, ESX-STATUS, ESX-STORAGE… Thank you

Hi, The vCenter connector is very good, but it lacks a feature that, for me, is essential. Alerts at the vCenter level only are not detected.I found some requests on GitHub or on TheWatch:https://github.com/centreon/centreon-plugins/issues/3854https://thewatch.centreon.com/infra-monitoring-platform-7/monitoring-vcenter-alarm-not-datacenter-or-cluster-952https://github.com/centreon/centreon-plugins/issues/2983  Many of these alarms (at the vCenter level) concern critical elements of the VMware infrastructure (kms, licence, lifecycle, certificate, identity provider,etc...).It would be a good idea to include these alarms.Best regards,

Hi, Would it be possible to add to the https certificate check option to choose which certificate in the chain (e.g., root, intermediate, or leaf/server) is checked?

Hello,I would like to inform you that we are monitoring Fortis and Palo Alto firewalls.On Fortis, you can monitor certificates and licenses, but on Palo Alto, you cannot monitor either of them.I have looked at the Palo Alto plugin and it does not include this feature. Is it possible to monitor it?Here are two examples, one with Palo Alto and one with Fortis: 

the plugin is using the Rubrik API, but if you query for a single backup job it could take minutes to complete in a bigger environment with a lot of backup jobs. if you are using curl and the API with a query object that is using a job name, the query finish within 1-2 seconds. curl -H "content-type:application/json" -H "authorization: Bearer xxxxxxxxx" -H "accept:application/json" 'https://xxxxxx.xxxx.com/api/v1/job_monitoring?limit=500&object_name=my-backup-job-name' | jq looks like the plugin is receiving the whole jobs list and than doing a selection, this could be optimized by building the query URL like in the curl command, so you receive very fast the result and have not to wait minutes (timeout of the check and the centengine default timeout is too low)

Bonjour,Nous utilisons le plugin Fortigate pour monitorer nos firewalls en SNMP, le discovery du service "Interfaces" fonctionne bien mais Nous aurions voulu mettre en place le discovery pour le mode "vpn".Actuellement le check du mode vpn est un check global qui remonte tout le temps Critical.Fortigate fait la différence entre le check de l'interface d'un tunnel VPN (qui peut être UP) et le check du VPN en lui-même avec toutes les phases 2 (Qui peuvent être down).Nous avons donc actuellement 2 checks distincts or il faudrait que le discovery vpn remonte tout les vpn+phase deux de manière indépendante (Il y en a des centaines par équipements en moyenne).Nous avons créer des commandes de Macro et Discover pour le mode vpn en en modifiant le script perl basé sur le discover du interface (En ajoutant les sections pour les paramètres --disco-show et --disco-format).Cette solution ne fonctionne pas...Y a t'il un autre moyen d'automatiser la création de ces services ?Cordialement conf comman

Hi,The Fortinet Fortigate SNMP already have the ability to filter sd-wan links by name.W'll be great if a new Disvery Rule to create Services by individual sd-wan links.Using just one service to all sd-wans links can obscure a new CRITICAL error when multiples links fail, and creating one service per sd-wan link can be massive when I manage 500+ Fortigates each with 10+ sdwan link.We need to create SD-WAN services in the same way that we create Interfaces services… Thnaks

Hi,Could you please add interface filter to --plugin=network::fortinet::fortigate::snmp::plugin --mode=sdwan.Currently it is only possible to filter by ID, VDom and Name. We have devices where only MPLS is active or only Inet is active. For example:checking sd-wan 'emea_hub' [vdom: root] [interface: emea-inet]    state: up    traffic in: 0.00 b/s, out: 0.00 b/s, bi: 0.00 b/s    latency: 53.682ms    jitter: 0.072ms    packet loss: 0.000%checking sd-wan 'emea_hub' [vdom: root] [interface: emea-mpls]    state: down    traffic in: 0.00 b/s, out: 0.00 b/s, bi: 0.00 b/s    latency: 0.000ms    jitter: 0.000ms    packet loss: 100.000% If I filter using name as emea_hub I will get critical alert. So I need to filter by interface name. bash-5.1$ /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl --plugin=network::fortinet::fortigate::snmp::plugin --mode=sdwan --hostname=1.2.3.4 --snmp-version='2c' --snmp-community='acb'  --warning-traffic-in='' --critical-traffic-in='' --warning-traffic-o