[jira] [Work logged] (GOBBLIN-1790) Add and cleanup fields to job status states and observability events

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GOBBLIN-1790?focusedWorklogId=847025&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-847025 ]

ASF GitHub Bot logged work on GOBBLIN-1790:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Feb/23 18:33
            Start Date: 22/Feb/23 18:33
    Worklog Time Spent: 10m 
      Work Description: Will-Lo opened a new pull request, #3649:
URL: https://github.com/apache/gobblin/pull/3649

   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - [ ] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1790
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if applicable):
   
   In GaaS, the observability events are still missing a few fields:
   1. Job Orchestration time
   
   2. Flowgraph edge ID
   
   3. Spec executor ID
   
   4. Azkaban user (if eligable)
   
   Additionally, the job start time field is inaccurate as it is set from multiple GTE events. We should be tracking it from a consistent point in the Gobblin Job, otherwise it will not be accurate when measuring the job runtime.
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   
   ### Commits
   - [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 847025)
    Remaining Estimate: 0h
            Time Spent: 10m

> Add and cleanup fields to job status states and observability events
> --------------------------------------------------------------------
>
>                 Key: GOBBLIN-1790
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1790
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-service
>            Reporter: William Lo
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In GaaS, the observability events are still missing a few fields:
> 1. Job Orchestration time
> 2. Flowgraph edge ID
> 3. Spec executor ID
> 4. Azkaban user (if eligable)
> Additionally, the job start time field is inaccurate as it is set from multiple GTE events. We should be tracking it from a consistent point in the Gobblin Job, otherwise it will not be accurate when measuring the job runtime.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)