[
https://issues.apache.org/jira/browse/GOBBLIN-1764?focusedWorklogId=839752&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-839752
]
ASF GitHub Bot logged work on GOBBLIN-1764:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Jan/23 18:59
Start Date: 17/Jan/23 18:59
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on PR #3623:
URL: https://github.com/apache/gobblin/pull/3623#issuecomment-1385907611
I read the description of the PR, can you please elaborate more what benefit
GaaSObservabilityEvents has over a GobblinTrackingEvent with
name="GaaSObservabilityEvent". How is it more easily queryable compared to
GobblinTrackingEvent? Is the frequency of emission is the only benefit?
Issue Time Tracking
-------------------
Worklog Id: (was: 839752)
Time Spent: 2h 20m (was: 2h 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: 2h 20m
> 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)
