You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stefan Richter (Jira)" <ji...@apache.org> on 2024/01/24 14:07:00 UTC
[jira] [Resolved] (FLINK-33696) FLIP-385: Add OpenTelemetryTraceReporter and OpenTelemetryMetricReporter
[ https://issues.apache.org/jira/browse/FLINK-33696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Richter resolved FLINK-33696.
------------------------------------
Resolution: Done
merged in 7db2ecad
> FLIP-385: Add OpenTelemetryTraceReporter and OpenTelemetryMetricReporter
> ------------------------------------------------------------------------
>
> Key: FLINK-33696
> URL: https://issues.apache.org/jira/browse/FLINK-33696
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Metrics
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
> Priority: Major
> Fix For: 1.19.0
>
>
> h1. Motivation
> [FLIP-384|https://cwiki.apache.org/confluence/display/FLINK/FLIP-384%3A+Introduce+TraceReporter+and+use+it+to+create+checkpointing+and+recovery+traces] is adding TraceReporter interface. However with [FLIP-384|https://cwiki.apache.org/confluence/display/FLINK/FLIP-384%3A+Introduce+TraceReporter+and+use+it+to+create+checkpointing+and+recovery+traces] alone, Log4jTraceReporter would be the only available implementation of TraceReporter interface, which is not very helpful.
> In this FLIP I’m proposing to contribute both MetricExporter and TraceReporter implementation using OpenTelemetry.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)