[
https://issues.apache.org/jira/browse/FLINK-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953275#comment-15953275
]
ASF GitHub Bot commented on FLINK-5090:
---------------------------------------
Github user zentol commented on a diff in the pull request:
https://github.com/apache/flink/pull/3348#discussion_r109386391
--- Diff: docs/monitoring/metrics.md ---
@@ -657,6 +657,24 @@ Thus, in order to infer the metric identifier:
<td>outPoolUsage</td>
<td>An estimate of the output buffers usage.</td>
</tr>
+ <tr>
+ <td rowspan="4">Network.<Input|Output>.<gate><br />
+ <strong>(only available if
<tt>taskmanager.net.detailed-metrics</tt> config option is set)</strong></td>
+ <td>total-queue-len</td>
+ <td>Total number of queued buffers in all input/output channels.</td>
+ </tr>
+ <tr>
+ <td>min-queue-len</td>
--- End diff --
These are not in sync with the actual metric names.
> Expose optionally detailed metrics about network queue lengths
> --------------------------------------------------------------
>
> Key: FLINK-5090
> URL: https://issues.apache.org/jira/browse/FLINK-5090
> Project: Flink
> Issue Type: New Feature
> Components: Metrics, Network
> Affects Versions: 1.1.3
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
>
> For debugging purposes, it is important to have access to more detailed
> metrics about the length of network input and output queues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)