[ 
https://issues.apache.org/jira/browse/GOBBLIN-2018?focusedWorklogId=910751&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910751
 ]

ASF GitHub Bot logged work on GOBBLIN-2018:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Mar/24 18:53
            Start Date: 20/Mar/24 18:53
    Worklog Time Spent: 10m 
      Work Description: Will-Lo commented on PR #3881:
URL: https://github.com/apache/gobblin/pull/3881#issuecomment-2010367619

   Opentelemetry decouples metrics emission from the way it reads from your 
metrics. The metric reader specification is here: 
https://github.com/open-telemetry/opentelemetry-specification/blob/v1.13.0/specification/metrics/sdk.md#metricreader
   
   So essentially you can have pluggable exporters that work with any reader, 
you can have the reader follow some aggregation and other behaviors e.g. 
scheduled, and exporters only deal with sending metrics to a backend system 
over a communication mechanism.
   
   The purpose of using the in-memory metric reader is to read directly from 
the metrics instead of having to wait for the scheduled reader that is the 
default behavior. This helps with avoiding race conditions in tests although 
care needs to be taken with the aggregation settings (left as default similar 
to the scheduled reader for now). 




Issue Time Tracking
-------------------

    Worklog Id:     (was: 910751)
    Time Spent: 40m  (was: 0.5h)

> Use Opentelemetry for sending metrics with GaaS Observability Events
> --------------------------------------------------------------------
>
>                 Key: GOBBLIN-2018
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2018
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-service
>            Reporter: William Lo
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently GaaS sends events via Kafka to get insights on flows in aggregate 
> and enable the ability for users to create queries and dashboards.
> For alerts, to support metrics based alerting from the same information, we 
> want to integrate Opentelemetry for a more modern multi dimensional metrics 
> experience that integrates with more backend systems.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to