From commits-return-29178-archive-asf-public=cust-asf.ponee.io@pulsar.apache.org Fri May 17 00:09:40 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 6C77C18066B for ; Fri, 17 May 2019 02:09:40 +0200 (CEST) Received: (qmail 74590 invoked by uid 500); 17 May 2019 00:09:39 -0000 Mailing-List: contact commits-help@pulsar.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pulsar.apache.org Delivered-To: mailing list commits@pulsar.apache.org Received: (qmail 74581 invoked by uid 99); 17 May 2019 00:09:39 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 May 2019 00:09:39 +0000 From: GitBox To: commits@pulsar.apache.org Subject: [GitHub] [pulsar] rdhabalia opened a new pull request #4290: [pulsar-broker] add broker-add-latency metrics Message-ID: <155805177968.32075.1347426264141650187.gitbox@gitbox.apache.org> Date: Fri, 17 May 2019 00:09:39 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit rdhabalia opened a new pull request #4290: [pulsar-broker] add broker-add-latency metrics URL: https://github.com/apache/pulsar/pull/4290 ### Motivation When user sees high publish-latency at client side then we need exact break-down metrics at server side which can give clear idea about customer impact. right now, we have add-entry latency for the managed-ledger to capture latency while adding entry to bookie. However, it would be great if we have two separate latencies: 1. e2e broker publish-latency (including request waiting time into the queue) and 2. ML add latency while adding entry to bookie (broker to bookie). So, adding 1st latency metrics to capture e2e broker publish-latency. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services