From 6f0cbe7212ba9124488d13e00a24a23e083cb918 Mon Sep 17 00:00:00 2001
From: Alex Loddengaard <alexloddengaard@gmail.com>
Date: Tue, 29 Nov 2016 09:57:22 -0800
Subject: [PATCH] MINOR: doc fix related to monitoring consumer lag

Author: Alex Loddengaard <alexloddengaard@gmail.com>

Reviewers: Ewen Cheslack-Postava <ewen@confluent.io>

Closes #1814 from alexlod/consumer-lag-doc-fix
---
 docs/ops.html | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/docs/ops.html b/docs/ops.html
index f0b659c01af..ef889a39235 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -833,8 +833,11 @@ We do graphing and alerting on the following metrics:
       <td></td>
     </tr>
     <tr>
-      <td>Number of messages the consumer lags behind the producer by</td>
-      <td>kafka.consumer:type=ConsumerFetcherManager,name=MaxLag,clientId=([-.\w]+)</td>
+      <td>Number of messages the consumer lags behind the producer by. Published by the consumer, not broker.</td>
+      <td>
+        <p><em>Old consumer:</em> kafka.consumer:type=ConsumerFetcherManager,name=MaxLag,clientId=([-.\w]+)</p>
+        <p><em>New consumer:</em> kafka.consumer:type=consumer-fetch-manager-metrics,client-id={client-id} Attribute: records-lag-max</p>
+      </td>
       <td></td>
     </tr>
     <tr>