[
https://issues.apache.org/jira/browse/FLINK-20561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20561:
-----------------------------------
Labels: auto-deprioritized-major pull-request-available stale-minor (was:
auto-deprioritized-major pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add documentation for `records-lag-max` metric.
> ------------------------------------------------
>
> Key: FLINK-20561
> URL: https://issues.apache.org/jira/browse/FLINK-20561
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 1.11.0, 1.12.0
> Reporter: xiaozilong
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available,
> stale-minor
>
> Currently, there are no metric description for kafka topic's lag in f[link
> metrics
> docs|https://ci.apache.org/projects/flink/flink-docs-release-1.11/monitoring/metrics.html#connectors].
> But this metric was reported in flink actually. So we should add some docs
> to guide the users to use it.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
