-
Notifications
You must be signed in to change notification settings - Fork 55
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
IWF-512: Add start timestamp field to all events #541
Conversation
2ad27a3
to
2175081
Compare
@samuel27m let me know if this is the right approach. I wasn't 100% sure if these are the timestamp values you needed |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #541 +/- ##
==========================================
+ Coverage 65.80% 65.89% +0.08%
==========================================
Files 62 62
Lines 6849 6872 +23
==========================================
+ Hits 4507 4528 +21
- Misses 2063 2065 +2
Partials 279 279 ☔ View full report in Codecov by Sentry. |
WorkflowId: provider.GetWorkflowInfo(ctx).WorkflowExecution.ID, | ||
WorkflowRunId: provider.GetWorkflowInfo(ctx).WorkflowExecution.RunID, | ||
SearchAttributes: sas, | ||
StartTimestampInMs: ptr.Any(provider.GetWorkflowInfo(ctx).WorkflowStartTime.UnixMilli()), |
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.
why use the WorkflowStartTime
here? How does that relate to the time the workflow failed?
I was thinking something like this, however, I also thinking that the FAIL events should include the Endtimestamp too: Start events should only contain the
But then FAIL events should also include the
Which would be the same implementation in timestamps as the COMPLETE events have:
Let me know if I'm missing something here, but this is what I was thinking |
2d93ad0
to
1674796
Compare
This makes sense! Added now 👍 |
Thank you! 🎉 |
Description
Checklist
Related Issue
Closes #issue_number