[
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 auto-deprioritized-minor
pull-request-available (was: auto-deprioritized-major pull-request-available
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> pull-request-available
>
> 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)
