[jira] [Work logged] (GOBBLIN-1750) Emit GaaSObservabilityEvent to mark job summaries from gaas

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

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

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

                Author: ASF GitHub Bot
            Created on: 28/Nov/22 19:02
            Start Date: 28/Nov/22 19:02
    Worklog Time Spent: 10m 
      Work Description: Will-Lo opened a new pull request, #3610:
URL: https://github.com/apache/gobblin/pull/3610

   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-1750
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if applicable):
   
   Users of GaaS have a difficult time monitoring their flows. Regular metrics do not have the cardinality needed to effectively determine the status of a pipeline, and GTE are too broad and are hard for users to create meaningful queries from.
   
   This PR sets up the schema of an observability event which would be used as a monitoring baseline in GaaS
   
   ### 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: 829431)
    Remaining Estimate: 0h
            Time Spent: 10m

> Emit GaaSObservabilityEvent to mark job summaries from gaas
> -----------------------------------------------------------
>
>                 Key: GOBBLIN-1750
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1750
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-service
>            Reporter: William Lo
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> GobblinTrackingEvents work for service <-> service communication, but it is hard to set up alerts or write queries around them in the GaaS context, due to lacking all of the context and having varying amounts of details around the Gobblin job.
> We want to emit a single GaaS event for jobs running on GaaS that provides a summary and can be easily queryable/parseable for other systems and engines to quickly understand the status of a Gobblin job.



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