[
https://issues.apache.org/jira/browse/GOBBLIN-1764?focusedWorklogId=839131&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-839131
]
ASF GitHub Bot logged work on GOBBLIN-1764:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Jan/23 18:27
Start Date: 13/Jan/23 18:27
Worklog Time Spent: 10m
Work Description: Will-Lo opened a new pull request, #3623:
URL: https://github.com/apache/gobblin/pull/3623
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-1764
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
GobblinTrackingEvents are not suitable for observability platforms at scale
due to their frequency of emission and lack of standardized schema.
GaaSObservabilityEvents are a new events that provides a job summary from
pipelines in GaaS. It differs from GobblinTrackingEvents as it runs once per
job pipeline, and it intended to be easily queryable and alert on.
We want to emit this observability event from GaaS by deriving it from a
job's job status. Since this feature is Experimental and WIP, it is not
expected to fill out all of the fields immediately.
This creates a template for a configurable GaaSObservabilityEventProducer,
and the emission logic can be implemented by any derived class that will define
the message sending mechanism.
### 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: 839131)
Remaining Estimate: 0h
Time Spent: 10m
> Emit GaaSObservabilityEvent
> ---------------------------
>
> Key: GOBBLIN-1764
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1764
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-service
> Reporter: William Lo
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> GaaSObservabilityEvents are a new events that provides a job summary from
> pipelines in GaaS. It differs from GobblinTrackingEvents as it runs once per
> job pipeline, and it intended to be easily queryable and alert on.
> We want to emit this observability event from GaaS by deriving it from a
> job's job status. Since this feature is Experimental and WIP, it is not
> expected to fill out all of the fields immediately.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
