Skip to content

Conversation

fulmicoton
Copy link
Collaborator

It was stuck to 0 because I forgot to increment the guard upon creation.

It was stuck to 0 because I forgot to increment the guard upon creation.
@fulmicoton-dd fulmicoton-dd force-pushed the paul.masurel/bugfix-indexing-pipeline-counter-not-inc branch from a020ff1 to 1d96c6b Compare September 10, 2025 12:31
let indexing_pipelines_gauge_guard = OwnedGaugeGuard::from_gauge(indexing_pipelines_gauge);
let mut indexing_pipelines_gauge_guard =
OwnedGaugeGuard::from_gauge(indexing_pipelines_gauge);
indexing_pipelines_gauge_guard.add(1);
Copy link
Contributor

Choose a reason for hiding this comment

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

nitpick: I think the guard should do the increment in the constructor

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

agreed. i made the change

@rdettai-sk
Copy link

@fulmicoton for consitency we might want to wrap the index label with quickwit_common::metrics::index_label() so that user can opt out from the index level granularity using QW_DISABLE_PER_INDEX_METRICS

@fulmicoton-dd fulmicoton-dd force-pushed the paul.masurel/bugfix-indexing-pipeline-counter-not-inc branch 4 times, most recently from ceb655f to a337cdf Compare September 12, 2025 14:28
@fulmicoton-dd fulmicoton-dd force-pushed the paul.masurel/bugfix-indexing-pipeline-counter-not-inc branch from a337cdf to 570f538 Compare September 12, 2025 15:27
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.

4 participants