Skip to content

Conversation

@omercier
Copy link
Contributor

Description

PLEASE MAKE SURE THAT THE BRANCH PR INCLUDES JIRA TICKET ID (for centreon-internal)

Please include a short resume of the changes and what is the purpose of PR. Any relevant information should be added to help:

  • QA Team (Quality Assurance) with tests.
  • reviewers to understand what are the stakes of the pull request.

Fixes # (issue)

Type of change

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

Target serie

  • 22.10.x
  • 23.04.x
  • 23.10.x
  • 24.04.x
  • 24.10.x
  • master

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.

Checklist

Community contributors & Centreon team

  • I have followed the coding style guidelines provided by Centreon
  • I have commented my code, especially new classes, functions or any legacy code modified. (docblock)
  • I have commented my code, especially hard-to-understand areas of the PR.
  • I have rebased my development branch on the base branch (master, maintenance).

Copy link
Contributor

@tanguyvda tanguyvda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

back in the days, I've made a lot of camelCase syntaxes. Need to switch them to snake_case

@omercier

This comment was marked as resolved.

@omercier omercier requested a review from tanguyvda May 22, 2025 16:16
@omercier omercier marked this pull request as ready for review May 22, 2025 16:16
@omercier omercier requested a review from a team as a code owner May 22, 2025 16:16
@omercier omercier requested a review from sdepassio May 26, 2025 11:30
omercier and others added 23 commits June 27, 2025 17:27
- metrics naming looks ok: no unit redundancy in names
- instances and subinstances handled
- removed hosts events since theyre not relevant
- the headers were not displayed by log_curl_command
- rename url parameter to match specs
- enable smart sleep for events too
- rewrite end of write() function
@omercier omercier force-pushed the CTOR-1320-Enhance-sc-prometheus-gateway-apiv1-to-prometheus-gateway-events-apiv2-and-prometheus-gateway-metrics-apiv2 branch from c45dc0d to dad573e Compare June 27, 2025 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants