From dev-return-71565-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Wed Jul 18 20:16:05 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A56FC180636 for ; Wed, 18 Jul 2018 20:16:04 +0200 (CEST) Received: (qmail 75630 invoked by uid 500); 18 Jul 2018 18:16:03 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 75369 invoked by uid 99); 18 Jul 2018 18:16:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jul 2018 18:16:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A2263C00D3 for ; Wed, 18 Jul 2018 18:16:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id cyHCOdeBkcpw for ; Wed, 18 Jul 2018 18:16:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3228B5F3EF for ; Wed, 18 Jul 2018 18:16:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7806DE0F9A for ; Wed, 18 Jul 2018 18:16:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3577521EE2 for ; Wed, 18 Jul 2018 18:16:00 +0000 (UTC) Date: Wed, 18 Jul 2018 18:16:00 +0000 (UTC) From: "Michael Han (JIRA)" To: dev@zookeeper.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ZOOKEEPER-3092) Pluggable metrics system for ZooKeeper MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ZOOKEEPER-3092?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 16548197#comment-16548197 ]=20 Michael Han commented on ZOOKEEPER-3092: ---------------------------------------- [~eolivelli] I think this work does not depend on the ongoing maven work, a= nd we should treat the metric system interfaces as part of ZooKeeper instea= d of using external ones, for the same reason Robert mentioned, so we can h= ave full control over it which would give us more flexibilities over what w= e want to add / remove down the road. Please let me know if you have any co= ncerns of this approach (and I am also interested on hearing what others th= ink). Yes designing the metrics API is the first step. It does not have to be per= fect, and have everything other metric systems already have, and we can sta= rted from typical metrics types and a reporting interface. I am thinking we= can use=C2=A0org.apache.zookeeper.metrics as namespace. Once the first ver= sion of interfaces are defined, we could provide a set of default implement= ations. Then we can proceed to implement the feature of dynamically load an= external metrics reporting library. And some testings of course along the = way. Sounds a lot of work, but should be fun :).=C2=A0 It's up to you how you want to do the design work - a short design doc or a= pull request for the proposed interfaces, either would work. Also it's lik= ely we should use this Jira as an umbrella and create actual tasks under it= so this feature can be shipped incrementally. =C2=A0 > Pluggable metrics system for ZooKeeper > -------------------------------------- > > Key: ZOOKEEPER-3092 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3092 > Project: ZooKeeper > Issue Type: New Feature > Components: metric system > Reporter: Michael Han > Priority: Major > > ZooKeeper should provide a pluggable metrics system such that various met= rics can be collected and reported using different approaches that fit prod= uction monitoring / alert / debugging needs.=20 > Historically ZooKeeper provides four letter words and JMX which exposes c= ertain stats / metrics but they are not very flexible in terms of programma= tically accessing metrics and connecting metrics to different reporting sys= tems. > There are other projects that's already doing this which can be used for = reference, such as bookkeeper metrics service providers and hadoop metrics2= . -- This message was sent by Atlassian JIRA (v7.6.3#76005)