[
https://issues.apache.org/jira/browse/GOBBLIN-989?focusedWorklogId=352258&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-352258
]
ASF GitHub Bot logged work on GOBBLIN-989:
------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Dec/19 22:08
Start Date: 02/Dec/19 22:08
Worklog Time Spent: 10m
Work Description: autumnust commented on pull request #2835: GOBBLIN-989:
Track and report record level SLA in Gobblin Kafka Extra…
URL: https://github.com/apache/incubator-gobblin/pull/2835#discussion_r352884746
##########
File path:
gobblin-modules/gobblin-kafka-common/src/main/java/org/apache/gobblin/source/extractor/extract/kafka/KafkaExtractorStatsTracker.java
##########
@@ -249,6 +263,7 @@ public void updateStatisticsForCurrentPartition(int
partitionIdx, long readStart
this.workUnitState.setProp(KafkaUtils.getPartitionPropName(KafkaSource.STOP_FETCH_EPOCH_TIME,
partitionId),
Long.toString(stats.getStopFetchEpochTime()));
tagsForPartition.put(PROCESSED_RECORD_COUNT,
Long.toString(stats.getProcessedRecordCount()));
+ tagsForPartition.put(SLA_MISSED_RECORD_COUNT,
Long.toString(stats.getSlaMissedRecordCount()));
Review comment:
If `SLA_MISSED_RECORD_COUNT ` is added anyway, how to distinguish between
non-SLA-miss versus non-configured for whoever just monitoring the dashboard?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 352258)
Time Spent: 40m (was: 0.5h)
> Track and report record level SLA in Gobblin Kafka Extractor tracking event
> ---------------------------------------------------------------------------
>
> Key: GOBBLIN-989
> URL: https://issues.apache.org/jira/browse/GOBBLIN-989
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-kafka
> Affects Versions: 0.15.0
> Reporter: Sudarshan Vasudevan
> Assignee: Shirshanka Das
> Priority: Major
> Fix For: 0.15.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Track record level SLA in Gobblin Kafka Extractor tracking events. The SLA is
> measured as the difference between extract time and the log append time on
> the Kafka broker, if available in the Kafka consumer record.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)