Build better products with our product team.
Hi,We’ve got a question/suggestion about the « formatting » node and outputs messages of virtual curves.Let’s say 2 virtual curves are defined for traffic network, summing incoming interfaces on one hand, outgoing on the other. Since the same printf_msg is used for each virtual curve, it has to be generic. So, just reading the « status information », one can’t figure out which one is the incoming traffic an which is the outgoing.Ex of current output:Status informationOK: Traffic on data interfaces is OKTraffic SUM is: 15.32 Mb/sTraffic SUM is: 7.82 Mb/sFiguring it out requires to get to the « performance data » and is neither explicit nor convenient.Persona : ITOps teamsProblem to solve : same output message for all the set of metrics of a virtual curves serviceExpected outcome : customize output of virtual curves servicesPotential solution :Offer possibility to define a « comment » entry in the virtual curves definition section with free entry.Ex :"virtualcurve": { "sum_traffic_in": { "pattern": "^traffic_in$", "aggregation":"sum", "comment":"IN" }, "sum_traffic_out": { "pattern": "^traffic_out$", "aggregation":"sum", "comment":"OUT" } }Then formatting node could be :"formatting": { "change_bytes_network": 1, "custom_message_global": "Traffic on data interfaces is OK", "printf_msg": "Traffic %s SUM is: %s %s/s", "printf_var": "$self->{result_values}->{comment},$self->{result_values}->{value}, $self->{result_values}->{unit}" }And expected resultStatus informationOK: Traffic on data interfaces is OKTraffic IN SUM is: 15.32 Mb/sTraffic OUT SUM is: 7.82 Mb/sRegards
The old “Monitoring > Status Details > Services” nicely handles the short output (Status information column). In case output doesn’t fit the length of this column it wraps the content dynamically to show all of it.The new “Monitoring > Resource Status” doesn’t handle this the same way. Which might be quite inconvenient. It just cut the content at some point. Even in case where there is still place to display it. Would be nice to have it working as it is done in the old page.Moreover the service details pop-in for should indicate clearly where the extended info section (long_output) starts. Now this distinction is not visible - short_output and long_output are just displayed as one. These are some small things which keep us still away from upgrading to 24.10 and later releases.
Hello,I have a use case that required me to modify the script /usr/share/centreon/cron/centreon-backup.pl. As the SCP (SSH) port is not port 22, I modified lines 242 and 253 to specify the port in the scp command.It would be useful to be able to specify the port in the Centreon backup settings.Have a nice day!
Hello All ,Could we imagine to add functionality and some columns Disable the search button for a dynamic search (like proposition in the watch ) And maybe add to column:Next to conf Changed ==> Date of Conf Changed User who change conf …
Bonjour,Serait- il possible pour les prochaines versions de permettre l’agrandissement des champs dans les vues configurations ?Cordialement. Hello,Will it be possible to enlarge fields in the configuration form in future versions ?regards.
Hello. Please improve the capabilities of the hardware::ups::cyberpower::snmp::plugin1) Add a new "input-lines" mode similar to how it is implemented in the "hardware::ats::apc::snmp::plugin"Information about the state of sources A/B inputs can be obtained from the OID table: .1.3.6.1.4.1.3808.1.1.6.9.4 (ePDU2SourceStatusTable)From these OIDs we can obtain information about the current state of the ATS inputs: Name/OID: ePDU2SourceStatusSelectedSource.1; Value (Integer): sourceA (1) Name/OID: ePDU2SourceStatusSourceAVolStatus.1; Value (Integer): normal (1) Name/OID: ePDU2SourceStatusSourceBVolStatus.1; Value (Integer): normal (1) Name/OID: ePDU2SourceStatusSourceAFreqStatus.1; Value (Integer): normal (1) Name/OID: ePDU2SourceStatusSourceBFreqStatus.1; Value (Integer): normal (1) Name/OID: ePDU2SourceStatusPowerSupplySourceAStatus.1; Value (Integer): normal (1) Name/OID: ePDU2SourceStatusPowerSupplySourceBStatus.1; Value (Integer): normal (1) Name/OID: ePDU2SourceStatusRedundancyState.1; Value (Integer): atsFullyRedundant (2) From these OIDs we can create a perfdata for the Voltage and Frequency parameters: Name/OID: ePDU2SourceStatusSourceAVoltage.1; Value (Integer): 218 Name/OID: ePDU2SourceStatusSourceBVoltage.1; Value (Integer): 222 Name/OID: ePDU2SourceStatusSourceAFrequency.1; Value (Integer): 500 Name/OID: ePDU2SourceStatusSourceBFrequency.1; Value (Integer): 500 2) Add a new "time" mode similar to how it is implemented in the "hardware::ats::apc::snmp::plugin" OID:.1.3.6.1.4.1.3808.2.1.5.1.0 (mconfigClockDate.0); Example value: 2024/09/02 OID:.1.3.6.1.4.1.3808.2.1.5.2.0 (mconfigClockTime.0); Example value: 18:08:57The received time should be compared with the NTP source. 3) Add a new mode for checking the NMC operating time ("uptime")This mode can be simply copied from the plugin "hardware::pdu::apc::snmp::plugin" 4) Add a new environment sensor check mode ("environment" mode):OID space environmentSensor2 (1.3.6.1.4.1.3808.1.1.8) is suitable for obtaining information about temperature (C) and humidity (%)MIB and snmpalk files are attached: https://github.com/user-attachments/files/16846878/CyberPower-ATS-PDU44005.zipThank you
We would like to have a Report (for MBI) that summarizes the Flapping Services.For example:Some network interfaces of a switch having packetloss, but only a few times like a loose contact. As we don’t want spam notification, this is covered as a softstate and not as a hardstate.But if this happens multiple times, it should be possible to report these abnormalities, ex. every month for a review. It could be a indication for a broken cable oder fiber.We don’t want to change the checks to get a hardstate, as this is no problem. But if it repeats multiple times, we would be able to see services with these behave to check for incident/problems.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.