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
Collect queue growth events and bytes metrics when PQ is enabled. #14554
Changes from 16 commits
00bf51c
79f6f25
efa6bbb
0aee22b
ab2cd72
ebbd611
ac12193
57e4f41
1fcb75b
5dbf383
b9d5ae7
2074d68
78d5110
34a22a3
358864a
57848bc
5332935
2b074a8
3c72ff3
a188ab6
724852d
c6a772c
c89e369
816ea2c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -56,7 +56,7 @@ def block_until(limit_seconds, &condition) | |
|
||
before :all do | ||
clear_data_dir | ||
settings = mock_settings("config.reload.automatic" => true) | ||
settings = mock_settings("config.reload.automatic" => true, "queue.type" => "persisted") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We have separate PQ and MQ tests in CI. Will this override them so that we only test PQ? Should we instead guard our specs to only validate the presence of our PQ-related metrics when the PQ is active? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This only helps us to validate the structure shape defined in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. TODO: don't enable the PQ for all of the shared tests in order to validate behavior of the PQ in just one of those tests. I recently worked with this shared context so I can see if I can find a way to limit the scope in which we have to incur the cost of spooling up PQ's. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. PR here -> mashhurs#4 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Great approach to apply specific setting through the context:
|
||
config_source = make_config_source(settings) | ||
config_source.add_pipeline('main', "input { generator {id => 'api-generator-pipeline' count => 100 } } output { dummyoutput {} }") | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yaauie, I need your review these important lines. Want to be sure every single point we are going to deliver to the end-user shouldn't be missed. Should be concise!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sweet. I had been working on the docs and have just rebased and made a PR against your branch -> mashhurs#3