-
Notifications
You must be signed in to change notification settings - Fork 85
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
Add support for monitors #547
base: master
Are you sure you want to change the base?
Conversation
Test Config:
Test: Test Output:
test-reports
|
I like the idea, but can you rename this to something like "monitoring jobs" or similar? It's not really clear what "profiler" is supposed to mean in the context of op-test. |
how about |
That works I guess. It's a little redundant since there's not much else we'd be monitoring, but I'm not that fussed. |
ya, right, |
test pending... |
6424629
to
ba0d586
Compare
result:
$ cat monitors |grep -v ^# $ ls -lrt test-reports/latest/
$ tail -10 test-reports/latest/20191209134147-lparstat_1.log
$ tail -10 test-reports/latest/lparstat_1
|
@oohal Have addressed all comments, pls merge if no further comments, Tnx! |
Let's add support for monitors to framework, this would help us capture the snapshot of system details through any user provided commands running in a predefined frequent intervals and store in a file in test-reports which then can be used for further processing later. Usage: `monitors` file in the basepath documents how user can create one monitor instance and running the test with `--enable-monitors` will allow the framework to enable the monitor threads run in parallel to the test and collect the output and monitor threads gets stopped at the end of tests and additional regular expression will help to extract useful information in the final output file. Signed-off-by: Satheesh Rajendran <[email protected]>
rebased... |
@oohal pls help merge if no further comments, tnx! |
4d0cb14
to
b976629
Compare
Let's add support for monitors to framework,
this would help us capture the snapshot of system
details through any user provided commands running
in a predefined frequent intervals and store in a
file in test-reports which then can be used for
further processing later.
Usage:
monitors
file in the basepath documents howuser can create one monitor instance and running the
test with
--enable-monitors
will allow the frameworkto enable the monitor threads run in parallel to the
test and collect the output and monitor threads gets
stopped at the end of tests and additional regular expression
will help to extract useful information in the final output file.
Signed-off-by: Satheesh Rajendran [email protected]