argoproj / argoproj/argo-workflows
Expose workflow start and finish time
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
Is this a BUG REPORT or FEATURE REQUEST?:
Feature request
What happened:
we want to log duration for success workflow
What you expected to happen:
should expose both finishedAt & startedAt value as global variables.
status:
finishedAt: 2019-04-17T18:37:21Z
....
startedAt: 2019-04-17T18:37:11Z
We currently have workflow.status for exit-handler to provide some information for user, but we want to further provide duration and startTime for user debug/logging purpose.
Environment:
-
Argo version:
v2.3.0-rc1 -
Kubernetes version :
v1.11.8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing workflow.status and the exit-handler in the Argo workflow status path; the issue names no files or tests. Confirm how startedAt and finishedAt should be exposed as global variables, then add coverage showing both timestamps are available for duration and debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100