-
Notifications
You must be signed in to change notification settings - Fork 397
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
fix(server): re-enable prometheus counters. #3304
Conversation
Tested and prometheus counters are working again. 👍🏼 I'll redo the panels created in #3297 on top of this working PR and raise the dashboard related one. |
|
Im adding an integration test to test if metrics are enabled and this will be ready. |
5972cfc
to
4fb428a
Compare
706816e
to
922a5c4
Compare
So, if the "test-performance" target does not run (it has a skip if the user can't execute anything using "sudo -n" (with no password)) then I'll have to run the performance tests in a jenkins runner or change the runner config a bit. Lets see.
Test passes in regular github runner. It starts tracee using sudo and makes sure it ends at the end of the test as you can see in the code. |
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.
LGTM
- create testutils/tracee to start/stop tracee using sudo - test if --healthz works - test if --metrics works - test if --pprof works
- test if metrics are enabled on each PR
This brings two new panels to the dashboard: - Heap - GC And makes some minor changes to the existing panels.
5545f3f
to
f9baadd
Compare
Commit: 0213c08 ("tracee: add ready callback") made prometheus stats to stop being registered due to a timing issue. This patch re-enables it by registering prometheus counters in the callback function itself instead of in Tracee.New() (too early).
Fixes: #3303