Skip to content

fix(pattern): Fix feature flag for enabling pattern persistence #18216

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
merged 1 commit into from
Jun 24, 2025

Conversation

chaudum
Copy link
Contributor

@chaudum chaudum commented Jun 24, 2025

What this PR does / why we need it:

PR #17737 introduced a feature to persist detected patterns on the pattern ingesters. And while there is a dedicated global config PatternPersistence and a per-tenant config PatternPersistenceEnabled, none of these were honoured, because for writing the patterns to the distributor, the same writer (and its config) as for persisting aggregated metrics is used. So, when aggregated metrics is enabled, also patterns were automatically written/persisted as well.

Signed-off-by: Christian Haudum <christian.haudum@gmail.com>
@chaudum chaudum added type/bug Somehing is not working as expected backport k260 labels Jun 24, 2025
@paul1r paul1r marked this pull request as ready for review June 24, 2025 19:52
@paul1r paul1r requested a review from a team as a code owner June 24, 2025 19:52
@paul1r paul1r merged commit c167800 into main Jun 24, 2025
68 checks passed
@paul1r paul1r deleted the chaudum/fix-pattern-persistence-main branch June 24, 2025 19:52
loki-gh-app bot pushed a commit that referenced this pull request Jun 24, 2025
Signed-off-by: Christian Haudum <christian.haudum@gmail.com>
(cherry picked from commit c167800)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport k260 size/M type/bug Somehing is not working as expected
2 participants