Skip to main content

    Filter by idea status

    Filter by product

    629 Ideas

    Cm123Builder **

    Create simple Availability graph for number of host and services and there status.Needs Votes

    Hello, I suggest creating a new dashboard or enhancing the existing one (Availability)within Centreon to provide a comprehensive view of the total number of services and hosts, along with their status. This dashboard should prominently display information such as number of OK, Critical, Warning, Unknown, and Pending services/host statuses in real time.Key Features of the Dashboard:Live Status Updates: Display the total number of services and hosts  and status in real time, allowing us to quickly identify any issues or anomalies. Different Time Frames: Provide options to view status trends over different time frames (e.g., daily, weekly, monthly) for historical analysis and trend identification. User-Friendly Interface: Design the dashboard with a focus on user experience, ensuring that information is presented clearly and intuitively. Impactful Visualizations: Utilize visual elements such as charts, graphs, and color-coded indicators to make the dashboard visually engaging and easy to interpret.Benefits:Improved Monitoring Efficiency: The dashboard will enable us to monitor a large volume of data more efficiently, reducing manual effort and streamlining decision-making. Real-Time Insights: With live status updates, we can promptly address issues and maintain optimal performance across our infrastructure. Historical Analysis: The ability to view status trends over time will facilitate trend analysis, proactive maintenance, and performance optimization.I believe that implementing this enhanced monitoring dashboard will significantly enhance our monitoring capabilities and contribute to a more proactive and efficient IT environment.Thank youcm123

    jstagerBuilder *

    Auto Discovery - regular automatic execution/schedule for servicesNeeds Votes

    Hello all,As it is already possible to automate and schedule the automatic discovery of new hosts.We want to be able to do the same with automatic service discovery.Indeed, this automation process has already existed for a few years for the hosts discovery but will be much more useful for the services configurations.A host's services are added and removed much more regularly than a host itself.This is not convenient that auto discovery for services remains manual and cannot be automatically scheduled. Indeed, we have autodiscovery templates for services but these must be activated manually each time an network interface is added on a host.It would also be very convenient if the services corresponding to the interfaces could be activated and deactivated depending on whether the interface is admin-up or admin-down.Today in the state of this manually-autodiscovery-service-process as soon as a virtual or physical interface is added we are forced to run several different templates for a single host. It will be nice to don’t have to worry about this and don’t wast time for that.Indeed today we scan (manually) and add and active all the serivices-checks for all the interfaces of a host whether they are admin-up or admin-down in order to avoid executing the manual-autodiscovery with many templates on many hosts every 2 days. It would be great if these jobs ran automatically at scheduled intervals. Thanks a lot

    jstagerBuilder *

    A more user-friendly search barReleased

    Since the new resources status pages, it became very difficult and no user-friendly to filter the results.Before, with the deprecated pages, it had different search fields "hosts”, “services”, “ouptut”, ..." and different selection fields. This was simple for any user, it was fast and efficient... … But today with this new single search field all research becomes too complicated. I have been an experienced Centreon user for 10 years, we have a 1000 hosts business version, but I am saddened to see that Centreon has become no user-firendly. In fact, all my users tell me that they can no longer find anything with this new single search bar. Today my users must to write long and unclear filters themselves, whereas they didn't have to worry about that before. They often don't know how to do it, they don't know if something is missing, they don't understand, it's too complicated for them and for an experienced users. Today my users must know the directives "s.description:, h.name:, information:, ...." whereas they did not have to worry about this before. Which is mission impossible for a normal user who has neither work nor time to waste, or not the desire to know all the subtleties of Centreon . Today my users must know the regex syntax. for example when they simply look for a network interface, otherwise they get error "Bad regex format 'HundredGigE0/1/1/0'". it is necessary to explain to them they must escape the regex with characters \. It's too complicated for a standard users and so annoying for an experienced users. Before they didn't have to worry about that. Since upgrade 22.04 to 23.04 it is no longer possible to search for results in the "long_output" tables even with the "information:" directive. Obviously this search function, although essential, was deliberately removed,  probably to prevent possible performance problems of the few customers who have very gigantic databases. Although it worked correctly for most centreon customers. I had no performance problem when we used this search on our database with more of 500 GB for 25k services.  proposals :Return of multiple search fields by default as in deprecated pages for simple use. And add an unfold button to access the expert search field corresponding to the new the single field. Have a possibility to activate or deactivate the search in the "long_output" fields. By default activate and have the possibility of deactivating it for who want this, like large clients with performance problems. Thank a lot 

    dbergoSteward *

    New Plugin for Monitor Datacore with REST ApiReleased

    Hi, Note● The RestAPI documentation starts from here:https://docs.datacore.com/RESTSupport-WebHelp/RESTSupport-WebHelp/Welcome.htm● Two headers should be passed in every request:https://docs.datacore.com/RESTSupport-WebHelp/RESTSupport-WebHelp/Sending_Requests.htm○ ServerHost: full computer name or IP address○ Authorization: Basic UsernamePassword● URL Structure Request Examples:https://docs.datacore.com/RESTSupport-WebHelp/RESTSupport-WebHelp/URL_Structure_Request_Examples.htm● Full documentation:https://docs.datacore.com/RESTSupport-WebHelp/RESTSupport-WebHelp/RESTReferenceGuide.htmlOur primary request is to monitor “BytesAllocatedPercentage” of a “Disk Pool”To monitor it we have to make two step:● Manually found the ID of the pool we are interested - function “Get Pools”https://docs.datacore.com/RESTSupport-WebHelp/RESTSupport-WebHelp/RESTReferenceGuide.html#OperationDetails_ID0EAZBI● Monitor the Performance - function “Get Performance”https://docs.datacore.com/RESTSupport-WebHelp/RESTSupport-WebHelp/RESTReferenceGuide.html#OperationDetails_ID0ELQBIManually found the ID the the pollers we are interested-bash-4.2$ curl -k -u <username>:<password> -H"ServerHost:<hostaddress>"https://<hostaddress>/RestService/rest.svc/1.0/pools?server=<hostname> | python -m json.tool% Total % Received % Xferd Average Speed Time TimeTime CurrentDload Upload Total SpentLeft Speed100 641 100 641 0 0 4700 0 --:--:-- --:--:----:--:-- 4713[{"Alias": "DAT1_Disk_pool_1","AutoTieringEnabled": true,"Caption": "DAT1_Disk_pool_1","ChunkSize": {"Value": 134217728},"DeduplicationState": 0,"Description": null,"ExtendedCaption": "DAT1_Disk_pool_1 on <hostname>","HasEncryption": false,"Id":"0C0EB462-D423-41FC-8521-5FAF72FD811A:{0b8bdf98-85fa-11ed-af64-30e17151f46f}","InSharedMode": false,"Internal": false,"IsAuthorized": true,"MaxTierNumber": 3,"PoolMode": 1,"PoolStatus": 0,"PresenceStatus": 1,"SMPAApproved": false,"SectorSize": {"Value": 512},"SequenceNumber": 413855939,"ServerId": "0C0EB462-D423-41FC-8521-5FAF72FD811A","SharedPoolId": null,"SupportsEncryption": true,"TierReservedPct": 3,"Type": 0}]Monitor the performance of a poll with a custom Centreon commandNormal command-bash-4.2$ /usr/lib/centreon/plugins//centreon_protocol_http.pl--plugin=apps::protocols::http::plugin --mode=json-content--hostname=<hostaddress> --proto='https' --port='443'--credentials --username='<user>' --password='<password>' --basic--urlpath='/RestService/rest.svc/1.0/performance/0C0EB462-D423-41FC-8521-5FAF72FD811A:{0b8bdf98-85fa-11ed-af64-30e17151f46f}'--header='Content-Type: application/json' --header='ServerHost:<hostname>' --lookup='$[0].BytesAllocatedPercentage'--threshold-value='values' --format-ok='BytesAllocatedPercentageare ok' --format-warning='BytesAllocatedPercentage are %{values}%'--format-critical='BytesAllocatedPercentage are %{values}%'--warning-numeric='35' --critical-numeric='50' --warning-string=''--critical-string='' --insecureOK: BytesAllocatedPercentage are ok | 'count'=1;;;0;'element_1'=29;0:35;0:50;; 'time'=0.067s;;;0;Debug output======> request sendGEThttps://<hostaddress>:443/RestService/rest.svc/1.0/performance/0C0EB462-D423-41FC-8521-5FAF72FD811A:%7B0b8bdf98-85fa-11ed-af64-30e17151f46f%7DAuthorization: Basic ****User-Agent: centreon::plugins::backend::http::useragentContent-Type: application/jsonServerHost: <hostname>======> response doneHTTP/1.1 200 OKCache-Control: privateDate: Fri, 26 May 2023 08:47:19 GMTServer: Microsoft-IIS/10.0Content-Length: 793Content-Type: application/jsonAccess-Control-Allow-Headers: Content-Type, Accept, ServerHost,AuthorizationAccess-Control-Allow-Methods: OPTIONS, GET, PUT, POST, DELETEAccess-Control-Allow-Origin: *Access-Control-Max-Age: 1728000Client-Date: Fri, 26 May 2023 08:47:20 GMTClient-Peer: <hostadress>:443Client-Response-Num: 1Client-SSL-Cert-Issuer: /CN=DataCoreSelfSignedCertClient-SSL-Cert-Subject: /CN=DataCoreSelfSignedCertClient-SSL-Cipher: ECDHE-RSA-AES256-GCM-SHA384Client-SSL-Socket-Class: IO::Socket::SSLX-AspNet-Version: 4.0.30319X-Powered-By: ASP.NET[{"CollectionTime":"\/Date(-62135596800000)\/","NullCounterMap":0,"TotalBytesTransferred":0,"TotalBytesRead":0,"TotalBytesWritten":0,"TotalBytesMigrated":0,"TotalReads":0,"TotalWrites":0,"TotalOperations":0,"BytesAllocated":0,"BytesAvailable":0,"BytesInReclamation":0,"BytesTotal":0,"PercentAllocated":0,"PercentAvailable":0,"TotalReadTime":0,"TotalWriteTime":0,"MaxReadTime":0,"MaxWriteTime":0,"MaxReadWriteTime":0,"MaxPoolBytes":0,"BytesReserved":0,"BytesAllocatedPercentage":0,"BytesReservedPercentage":0,"BytesInReclamationPercentage":0,"BytesAvailablePercentage":0,"BytesOverSubscribed":0,"EstimatedDepletionTime":0,"DeduplicationPoolPercentFreeSpace":0,"ExpectedDeduplicationPoolUsedSpace":0,"DeduplicationPoolUsedSpace":0,"DeduplicationPoolFreeSpace":0,"DeduplicationPoolTotalSpace":0}][{"CollectionTime":"\/Date(-62135596800000)\/","NullCounterMap":0,"TotalBytesTransferred":0,"TotalBytesRead":0,"TotalBytesWritten":0,"TotalBytesMigrated":0,"TotalReads":0,"TotalWrites":0,"TotalOperations":0,"BytesAllocated":0,"BytesAvailable":0,"BytesInReclamation":0,"BytesTotal":0,"PercentAllocated":0,"PercentAvailable":0,"TotalReadTime":0,"TotalWriteTime":0,"MaxReadTime":0,"MaxWriteTime":0,"MaxReadWriteTime":0,"MaxPoolBytes":0,"BytesReserved":0,"BytesAllocatedPercentage":0,"BytesReservedPercentage":0,"BytesInReclamationPercentage":0,"BytesAvailablePercentage":0,"BytesOverSubscribed":0,"EstimatedDepletionTime":0,"DeduplicationPoolPercentFreeSpace":0,"ExpectedDeduplicationPoolUsedSpace":0,"DeduplicationPoolUsedSpace":0,"DeduplicationPoolFreeSpace":0,"DeduplicationPoolTotalSpace":0}]Lookup XPath $[0].BytesAllocatedPercentage:Node value: 0Response time 0.061s