-
Notifications
You must be signed in to change notification settings - Fork 4
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
AJ-1524: tracing for submission monitor #2667
Conversation
pervasive 503s from swat tests. Jenkins retest. |
case _ => | ||
logger.error(s"error monitoring submission after $count times", throwable) | ||
logger.error(s"error monitoring submission after $count times: ${throwable.getMessage}", throwable) |
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.
ok, these changes aren't about tracing; this is about making it a little easier to see the error in question when searching logs
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
Ticket: https://broadworkbench.atlassian.net/browse/AJ-1524
Adds hopefully comprehensive tracing for the submission monitor
handleOutputs
method . Given that we see pretty long transactions related to workflows, hopefully this tracing helps us figure out what's taking so much time.Reviewers: the auto-formatter reformatted a bunch of code, I suggest ignoring whitespace when viewing the diff.
PR checklist
model/
, then you should publish a new officialrawls-model
and updaterawls-model
in Orchestration's dependencies.