Skip to content
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

chore: Add new field to "stats-report" log line in bloom gateway #14446

Merged

Conversation

chaudum
Copy link
Contributor

@chaudum chaudum commented Oct 10, 2024

What this PR does / why we need it:

This new field reports how many blocks have been processed in total in the multiplexed request.

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • Title matches the required conventional commits format, see here
    • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

This new field reports how many blocks have been proceesed in total in
the multiplexed request.

Signed-off-by: Christian Haudum <christian.haudum@gmail.com>
@chaudum chaudum marked this pull request as ready for review October 10, 2024 12:37
@chaudum chaudum requested a review from a team as a code owner October 10, 2024 12:37
@@ -83,6 +83,7 @@ func (p *processor) processTasksForDay(ctx context.Context, _ string, _ config.D

for _, t := range tasks {
FromContext(t.ctx).AddBlocksFetchTime(duration)
FromContext(t.ctx).AddProcessedBlocksTotal(len(tasksByBlock))
Copy link
Member

Choose a reason for hiding this comment

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

Just making sure this is correct: each task has exactly len(tasksByBlock) blocks?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, len(tasksByBlock) is the number of all blocks from multiple multiplexed requests.

There is another field Stats.ProcessedBlocks, which references the amount of blocks processed for the specific request (task).

Copy link
Member

Choose a reason for hiding this comment

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

Hm, I'm not sure I understand why we're adding len(tasksByBlock) for each task then

Copy link
Contributor Author

Choose a reason for hiding this comment

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

To see how many blocks are processed in a multiplexed request.
This is interesting for the -bloom-gateway.block-query-concurrency setting, which defines how many blocks are processed in parallel (as part of a multiplexed request).

@chaudum chaudum merged commit fc8250b into main Oct 10, 2024
62 checks passed
@chaudum chaudum deleted the chaudum/add-total-blocks-processed-to-bloom-gw-stats-log branch October 10, 2024 13:49
trevorwhitney pushed a commit that referenced this pull request Oct 10, 2024
)

This new field reports how many blocks have been processed in total in the multiplexed request.

Signed-off-by: Christian Haudum <christian.haudum@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants