8000 nhcb: Add global config option for convert_classic_histograms_to_nhcb by chardch · Pull Request #16226 · prometheus/prometheus · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

nhcb: Add global config option for convert_classic_histograms_to_nhcb #16226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

chardch
Copy link
@chardch chardch commented Mar 17, 2025

Addresses the global part of #13532

@chardch chardch force-pushed the global-convert-classic-histo-to-nhcb branch 3 times, most recently from 3511e1f to e6b3479 Compare March 17, 2025 23:11
Copy link
Member
@bwplotka bwplotka left a comment

Choose a reason for hiding this comment

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

Looks generally good, but I am leaving for PTO, so couldn't take very deep look (e.g. if we have a precedence for *bool pattern in our config).

LGTM as far I see (modulo nits) (:

@chardch chardch force-pushed the global-convert-classic-histo-to-nhcb branch from df1d683 to 818a191 Compare March 19, 2025 21:22
@chardch
Copy link
Author
chardch commented Mar 19, 2025

@krajorama or @beorn7 can either of you help review this?

@krajorama krajorama self-requested a review March 20, 2025 13:38
Copy link
Member
@krajorama krajorama left a comment

Choose a reason for hiding this comment

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

Looking good, I have some further suggestions.

Bartek asked if we should use *bool , but I don't see how we could avoid it. The other parameters that have global defaults are numbers (like scrape interval, timeout) so it's easy to just take the 0 value as not-set, but this is a bool.

The thing that has tripped us up before was making changes effective on reload of configuration. I don't have the time to check that now, but maybe you could try it out? See #13846

@chardch chardch force-pushed the global-convert-classic-histo-to-nhcb branch from 818a191 to 36b9695 Compare March 27, 2025 16:56
Copy link
Author
@chardch chardch left a comment

Choose a reaso 8000 n for hiding this comment

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

The thing that has tripped us up before was making changes effective on reload of configuration. I don't have the time to check that now, but maybe you could try it out? See #13846

Thanks for pointing this out @krajorama. I tested reloading prometheus with a config change to the convert classic hist to nhcb and the change was picked up. Did this by sending a SIGHUP to prometheus. Is there further considerations for this?

Regarding the sync part, I saw sync is only called here

sp.Sync(groups)
after the scrape config has been reloaded, so the new targets should have the new scrape config right? Is there a specific case to test here?

Addresses the global part of prometheus#13532

Signed-off-by: chardch <otwordsne@gmail.com>
@chardch chardch force-pushed the global-convert-classic-histo-to-nhcb branch from 36b9695 to 7c13bed Compare March 27, 2025 17:55
Signed-off-by: chardch <otwordsne@gmail.com>
@chardch chardch force-pushed the global-convert-classic-histo-to-nhcb branch from 7c13bed to 357b5ed Compare March 29, 2025 15:35
@chardch chardch requested a review from krajorama March 31, 2025 18:15
Copy link
Member
@krajorama krajorama left a comment

Choose a reason for hiding this comment

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

LGTM

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.

3775
4 participants
0