-
Notifications
You must be signed in to change notification settings - Fork 2
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 monitoring operation #121
Comments
Hi @bergos, to which repository does this need to be added? |
cristianvasquez
referenced
this issue
in zazuko/barnard59-base
Apr 26, 2022
cristianvasquez
referenced
this issue
in zazuko/barnard59-base
Apr 26, 2022
Pull request at: zazuko/barnard59-base#26 |
cristianvasquez
referenced
this issue
in zazuko/barnard59-base
Apr 26, 2022
cristianvasquez
referenced
this issue
in zazuko/barnard59-base
Apr 26, 2022
cristianvasquez
referenced
this issue
in zazuko/barnard59-base
Apr 26, 2022
cristianvasquez
referenced
this issue
in zazuko/barnard59-base
May 25, 2022
cristianvasquez
referenced
this issue
in zazuko/barnard59-base
Feb 27, 2023
Operation: throughput print the date-time of the first chunk occurrence print the total count + chunk per minute or interval
Smaller pull request at: zazuko/barnard59-base#28 |
As discussed with @cristianvasquez @giacomociti @mchlrch, we propose that instead of implementing specialized monitoring steps, there should be a built-in feature to allow observing existing steps in a pipeline. |
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There should be an operation that logs in specific intervals the throughput at a specific point in the pipeline. It should be available as raw and object operation.
The text was updated successfully, but these errors were encountered: