Skip to content

Release 20251100#5854

Merged
pkippes merged 30 commits into
masterfrom
release-20251100
Nov 17, 2025
Merged

Release 20251100#5854
pkippes merged 30 commits into
masterfrom
release-20251100

Conversation

@pkippes
Copy link
Copy Markdown
Contributor

@pkippes pkippes commented Nov 12, 2025

Community contributors

Description

Please include a short resume of the changes and what is the purpose of this pull request.
Any relevant information should be added to help reviewers to understand what are the stakes
of the pull request.

Fixes # (issue)
If you are fixing a github Issue already existing, mention it here.

Type of change

  • Patch fixing an issue (non-breaking change)
  • New functionality (non-breaking change)
  • Functionality enhancement or optimization (non-breaking change)
  • Breaking change (patch or feature) that might cause side effects breaking part of the Software

How this pull request can be tested ?

Please describe the procedure to verify that the goal of the PR is matched.
Provide clear instructions so that it can be correctly tested.

Any relevant details of the configuration to perform the test should be added.
To integrate this pull request into our core we need to add some automated tests to check the proper
functioning of this PR. Ideally we need the following informations:

  • SNMP: MIB files and full snmpwalk of enterprise branch (snmpwalk -ObentU -v 2c -c public address .1.3.6.1.4.1 > equipment.snmpwalk) or SNMP collections.
  • HTTP API (SOAP, Rest/Json, XML-RPC): the documentation and some curl examples (command with -v + output) or HTTP collections.
  • CLI: command line examples (command + result).
  • SQL: queries + results + column types or SQL collections.
  • JMX: mbean names and attributes.

If some information is confidential, such as logins or IP addresses, obfuscate them in what is sent
publicly and we'll get in touch with you by private message if this information is needed.

Checklist

  • I have followed the coding style guidelines provided by Centreon
  • I have commented my code, especially hard-to-understand areas of the PR.
  • I have rebased my development branch on the base branch (develop).
  • I have provide data or shown output displaying the result of this code in the plugin area concerned.

Centreon team (internal PR)

Description

PLEASE MAKE SURE THAT THE BRANCH PR INCLUDES JIRA TICKET ID

Please include a short resume of the changes and what is the purpose of this pull request.
Any relevant information should be added to help reviewers to understand what are the stakes
of the pull request.

Fixes # (issue)
If you are fixing a github Issue already existing, mention it here.
If you are fixing one or more JIRA ticket, mention it here too.

Type of change

  • Patch fixing an issue (non-breaking change)
  • New functionality (non-breaking change)
  • Functionality enhancement or optimization (non-breaking change)
  • Breaking change (patch or feature) that might cause side effects breaking part of the Software

How this pull request can be tested ?

Please describe the procedure to verify that the goal of the PR is matched.
Provide clear instructions so that it can be correctly tested.
Mention the automated tests included in this FOR (what they test like mode/option combinations).

Checklist

  • I have followed the coding style guidelines provided by Centreon
  • I have commented my code, especially hard-to-understand areas of the PR.
  • I have rebased my development branch on the base branch (develop).
  • In case of a new plugin, I have created the new packaging directory accordingly.
  • I have implemented automated tests related to my commits.
    • Data used for automated tests are anonymized.
  • I have reviewed all the help messages in all the .pm files I have modified.
    • All sentences begin with a capital letter.
    • All sentences end with a period.
    • I am able to understand all the help messages, if not, exchange with the PO or TW to rewrite them.
  • After having created the PR, I will make sure that all the tests provided in this PR have run and passed.

pkippes and others added 26 commits October 14, 2025 10:26
…WN when container is not found (#5814)

Refs: CTOR-1610
Co-authored-by: lucie-tirand <ldubrunfaut@CNTR-PORT-A198.localdomain>
Co-authored-by: Sylvain Cresto <scresto@centreon.com>
…n status for short output (#5819)

Co-authored-by: lucie-tirand <ldubrunfaut@CNTR-PORT-A198.localdomain>
Refs: CTOR-1986
…: ready in hardware mode CTOR-1949 (#5789)

Co-authored-by: Lucie Tirand <123162035+lucie-tirand@users.noreply.github.com>
Co-authored-by: lucie-tirand <ldubrunfaut@CNTR-PORT-A198.localdomain>
* Add missing username doc option

* Added version detection + tests

Refs:CTOR-1948
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: lucie-tirand <ldubrunfaut@CNTR-PORT-A198.localdomain>
Co-authored-by: omercier <32134301+omercier@users.noreply.github.com>

Refs: CTOR-1993
Co-authored-by: lucie-tirand <ldubrunfaut@CNTR-PORT-A198.localdomain>
Co-authored-by: sdepassio <114986849+sdepassio@users.noreply.github.com>
Co-authored-by: omercier <32134301+omercier@users.noreply.github.com>
…1951 (#5845)

Co-authored-by: lucie-tirand <ldubrunfaut@CNTR-PORT-A198.localdomain>

Refs: CTOR-1951
…TOR-1955 (#5844)

Co-authored-by: lucie-tirand <ldubrunfaut@CNTR-PORT-A198.localdomain>
Co-authored-by: sdepassio <114986849+sdepassio@users.noreply.github.com>
…value (mean/count) in getmetrics (#5815)

Refs: CTOR-1939
Co-authored-by: garnier-quentin <garnier.quentin@gmail.com>

Refs: CTOR-1613
Co-authored-by: garnier-quentin <garnier.quentin@gmail.com>

Follows #5770 by @garnier-quentin and includes:

- New modes for `cloud::prometheus::exporters::nodeexporter::plugin`:
  - uptime
  - interfaces
- Mode enhancement `cloud::prometheus::exporters::nodeexporter::mode::storage`: add discovery
- New plugin `network::hp::athonet::nodeexporter::api::plugin` with modes:
  - chf
  - dra
  - eir
  - licenses
  - mme
  - nrf
  - pcf
  - sgwc
  - smf
  - smsf
  - udm
  - udr
  - upf

Refs: CTOR-1628
…5835)

Co-authored-by: lucie-tirand <ldubrunfaut@CNTR-PORT-A198.localdomain>
Co-authored-by: sdepassio <114986849+sdepassio@users.noreply.github.com>
Co-authored-by: omercier <32134301+omercier@users.noreply.github.com>

Refs: CTOR-2012
…et not supported anymore (#5841)

Co-authored-by: omercier <omercier@centreon.com>

Refs: CTOR-837
@pkippes pkippes requested review from a team as code owners November 12, 2025 14:56
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Nov 12, 2025

Logo
Checkmarx One – Scan Summary & Details86c54bac-be7b-47db-ae4f-0085ada74722

New Issues (7)

Checkmarx found the following issues in this Pull Request

Severity Issue Source File / Package Checkmarx Insight
MEDIUM Use_of_Broken_or_Risky_Cryptographic_Algorithm /src/network/hp/athonet/alertmanager/api/custom/api.pm: 129
detailsIn , the application protects sensitive data using a cryptographic algorithm, md5_hex, that is considered weak or even trivially broken, in /src/n...
ID: gv0FLtkZ7hHxxsQHXay8NmtBKPA%3D
Attack Vector
MEDIUM Use_of_Broken_or_Risky_Cryptographic_Algorithm /src/network/hp/athonet/alertmanager/api/custom/api.pm: 125
detailsIn , the application protects sensitive data using a cryptographic algorithm, md5_hex, that is considered weak or even trivially broken, in /src/n...
ID: MSfHYLBNQKO7%2FolYBWVzw08rfJc%3D
Attack Vector
MEDIUM Use_of_Broken_or_Risky_Cryptographic_Algorithm /src/network/hp/athonet/nodeexporter/api/custom/api.pm: 131
detailsIn , the application protects sensitive data using a cryptographic algorithm, md5_hex, that is considered weak or even trivially broken, in /src/n...
ID: RLqIQkYf1dk4UANiwTqXY0rlPcU%3D
Attack Vector
MEDIUM Use_of_Broken_or_Risky_Cryptographic_Algorithm /src/network/hp/athonet/nodeexporter/api/custom/api.pm: 127
detailsIn , the application protects sensitive data using a cryptographic algorithm, md5_hex, that is considered weak or even trivially broken, in /src/n...
ID: IGEcb8HXT376J79ZTVYZ5FX7XT4%3D
Attack Vector
LOW Permissive_Regular_Expression /src/cloud/prometheus/exporters/nodeexporter/mode/uptime.pm: 125 Attack Vector
LOW Permissive_Regular_Expression /src/cloud/prometheus/exporters/nodeexporter/mode/interfaces.pm: 83 Attack Vector
LOW Permissive_Regular_Expression /src/cloud/prometheus/exporters/nodeexporter/mode/interfaces.pm: 83 Attack Vector

omercier
omercier previously approved these changes Nov 13, 2025
@pkippes pkippes merged commit 0b47145 into master Nov 17, 2025
66 of 67 checks passed
@pkippes pkippes deleted the release-20251100 branch November 18, 2025 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants