[
https://issues.apache.org/jira/browse/GOBBLIN-2079?focusedWorklogId=922052&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922052
]
ASF GitHub Bot logged work on GOBBLIN-2079:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jun/24 01:06
Start Date: 05/Jun/24 01:06
Worklog Time Spent: 10m
Work Description: Will-Lo opened a new pull request, #3962:
URL: https://github.com/apache/gobblin/pull/3962
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-2079
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
`GaaSJobObservabilityEvents` currently encapsulate both jobs and flows in
GaaS.
This is fine for single hop flows, but flows with multiple jobs encapsulated
in them now have a mix of job level events with the majority of metadata, and
flow level events which provide a better view to users when their flow fails at
any given point.
Since the data in both events differs vastly with most metadata only having
contextual sense in the job level event, we should separate job and flow level
events to their own respective event types.
This PR creates a new type of event, called `GaaSFlowObservabilityEvent`,
which contains the following metadata defined in this file:
gobblin-metrics-libs/gobblin-metrics-base/src/main/avro/GaaSFlowObservabilityEvent.avsc
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Unit tests
### 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: 922052)
Remaining Estimate: 0h
Time Spent: 10m
> GaaSObservabilityEvents should have a dedicated flow level event
> ----------------------------------------------------------------
>
> Key: GOBBLIN-2079
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2079
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: William Lo
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> GaaSJobObservabilityEvents currently encapsulate both jobs and flows in GaaS.
> This is fine for single hop flows, but flows with multiple jobs encapsulated
> in them now have a mix of job level events with the majority of metadata, and
> flow level events which provide a better view to users when their flow fails
> at any given point.
> Since the data in both events differs vastly with most metadata only having
> contextual sense in the job level event, we should separate job and flow
> level events to their own respective event types.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
