[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010947#comment-16010947
 ] 

ASF GitHub Bot commented on BOOKKEEPER-1067:
--------------------------------------------

GitHub user merlimat opened a pull request:

    https://github.com/apache/bookkeeper/pull/154

    BOOKKEEPER-1067: Add Prometheus stats provider

    Prometheus (https://prometheus.io) is a metrics collection system, similar 
but much more flexible than graphite.
    
    It would be good to expose the Bookie and BookKeeper client stats directly 
so that a Prometheus instance can collect them (and also check the process 
status and add alerts).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/merlimat/bookkeeper prometheus

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/bookkeeper/pull/154.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #154
    
----
commit 9395dcd5b77fc1f41f427a43dbe42582a1d4b5ea
Author: Matteo Merli <mme...@apache.org>
Date:   2017-05-14T05:43:25Z

    BOOKKEEPER-1067: Add Prometheus stats provider

----


> Add Prometheus stats provider
> -----------------------------
>
>                 Key: BOOKKEEPER-1067
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1067
>             Project: Bookkeeper
>          Issue Type: New Feature
>            Reporter: Matteo Merli
>            Assignee: Matteo Merli
>            Priority: Minor
>             Fix For: 4.5.0
>
>
> Prometheus (https://prometheus.io) is a metrics collection system, similar 
> but much more flexible than graphite. 
> It would be good to expose the Bookie and BookKeeper client stats directly so 
> that a Prometheus instance can collect them (and also check the process 
> status and add alerts).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to