[
https://issues.apache.org/jira/browse/FLINK-23411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764477#comment-17764477
]
Hangxiang Yu commented on FLINK-23411:
--------------------------------------
Thanks for the quick reply.
{quote}Anyway, I think best way would be to first think through OTEL/Traces
integration, add support for that, and then add those new checkpointing metrics
from this ticket in this new model. However it's indeed much more work
(including writing and voting on a FLIP)
{quote}
Yeah, Supprting OTEL/Traces integration makes sense.
Besides some task-level metrics like this, users could also report their
own-defined operator metrics to their own distributed tracing system which may
be traced together with other jobs or systems.
I could also try to improve this when I'm free if you also think it's helpful
for users.
{quote}One thing is that in order to not bloat metric system too much, we
should implement this as an opt-in feature, hidden behind a feature toggle,
that users would have to manually enable in order to see those metrics.
{quote}
Sure, I aggree. Thanks for the advice.
> Expose Flink checkpoint details metrics
> ---------------------------------------
>
> Key: FLINK-23411
> URL: https://issues.apache.org/jira/browse/FLINK-23411
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Affects Versions: 1.13.1, 1.12.4
> Reporter: Jun Qin
> Assignee: Hangxiang Yu
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.18.0
>
>
> The checkpoint metrics as shown in the Flink Web UI like the
> sync/async/alignment/start delay are not exposed to the metrics system. This
> makes problem investigation harder when Web UI is not enabled: those numbers
> can not get in the DEBUG logs. I think we should see how we can expose
> metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
