Skip to content

api: fix Graphite configuration validation - #49

Merged
themilchenko merged 3 commits into
masterfrom
themilchenko/gh-no-dont-call-stop-on-validate
Aug 7, 2026
Merged

api: fix Graphite configuration validation#49
themilchenko merged 3 commits into
masterfrom
themilchenko/gh-no-dont-call-stop-on-validate

Conversation

@themilchenko

Copy link
Copy Markdown
Contributor

This patch set contains bug fixes related to config reload and a test for graphite target removal.

The removal of the `graphite` section is handled by the same loop as
the http one, but goes through another code path. Check that the
exporters are stopped after such a reload.
`validate_graphite()` checked the metrics version by calling
`graphite.stop()`, which kills all running exporters. As
`apply_graphite()` skips initialization when the configuration is not
changed, any `config:reload()` that kept the graphite section as is
silently stopped the export.

Now the check does not touch the plugin.
The support check was performed for any configuration mentioning the
`graphite` section, including an empty one. Such a section does not
start any exporter, so there is nothing to check.

Now the check runs only if at least one graphite node is configured.
@themilchenko
themilchenko merged commit 5516288 into master Aug 7, 2026
8 checks passed
@themilchenko
themilchenko deleted the themilchenko/gh-no-dont-call-stop-on-validate branch August 7, 2026 11:08
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