You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by sijie <gi...@git.apache.org> on 2017/06/01 08:17:36 UTC
[GitHub] bookkeeper pull request #173: BOOKKEEPER-1085: Introduce the AlertStatsLogge...
GitHub user sijie opened a pull request:
https://github.com/apache/bookkeeper/pull/173
BOOKKEEPER-1085: Introduce the AlertStatsLogger
Introduce the AlertStatsLogger used to increment a metric whenever an event that should never happen is detected. Allow specifying an optional scope to better classify the error conditions
RB_ID=598662
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sijie/bookkeeper add_alert_state_logger
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bookkeeper/pull/173.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 #173
----
commit e28e6cb3e037e2c006162a998aabe6fb09214ac5
Author: Robin Dhamankar <rd...@twitter.com>
Date: 2015-03-10T19:59:45Z
BookKeeper: Introduce the AlertStatsLogger
Introduce the AlertStatsLogger used to increment a metric whenever an event that should never happen is detected. Allow specifying an optional scope to better classify the error conditions
RB_ID=598662
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] bookkeeper issue #173: BOOKKEEPER-1085: Introduce the AlertStatsLogger
Posted by sijie <gi...@git.apache.org>.
Github user sijie commented on the issue:
https://github.com/apache/bookkeeper/pull/173
added license header
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] bookkeeper issue #173: BOOKKEEPER-1085: Introduce the AlertStatsLogger
Posted by eolivelli <gi...@git.apache.org>.
Github user eolivelli commented on the issue:
https://github.com/apache/bookkeeper/pull/173
Sorry @sijie , While merging Rat reported an error, the new class AlertStatsLogger does not have a good license header
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] bookkeeper issue #173: BOOKKEEPER-1085: Introduce the AlertStatsLogger
Posted by sijie <gi...@git.apache.org>.
Github user sijie commented on the issue:
https://github.com/apache/bookkeeper/pull/173
This change is from Robin
`
commit e28e6cb3e037e2c006162a998aabe6fb09214ac5
Author: Robin Dhamankar <rd...@twitter.com>
Date: Tue Mar 10 12:59:45 2015 -0700
BookKeeper: Introduce the AlertStatsLogger
Introduce the AlertStatsLogger used to increment a metric whenever an event that should never happen is detected. Allow specifying an optional scope to better classify the error conditions
RB_ID=598662
`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] bookkeeper pull request #173: BOOKKEEPER-1085: Introduce the AlertStatsLogge...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/bookkeeper/pull/173
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---