[
https://issues.apache.org/jira/browse/GOBBLIN-1770?focusedWorklogId=841891&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-841891
]
ASF GitHub Bot logged work on GOBBLIN-1770:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 27/Jan/23 00:44
Start Date: 27/Jan/23 00:44
Worklog Time Spent: 10m
Work Description: Will-Lo merged PR #3630:
URL: https://github.com/apache/gobblin/pull/3630
Issue Time Tracking
-------------------
Worklog Id: (was: 841891)
Time Spent: 0.5h (was: 20m)
> Fix Serialization of GaaSObservabilityEvent by allowing null values for Issue
> details and and properties
> --------------------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-1770
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1770
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: William Lo
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When looking into the IssueRepository before the creation of
> GaaSObservabilityEvents, many issues do not populate their fields for details
> and summary. This is because the Issue details are composed of a stack trace,
> but since Issues can be composed of warn/error logs and stack traces, it is
> not guaranteed that every issue has a corresponding stack trace.
> However, from investigation it looks like the automated troubleshooter will
> always populate the issue severity, code, and summary.
> We should guard against this when generating a GaaSObservabilityEvent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
