beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bjchambers <>
Subject [GitHub] incubator-beam pull request #1024: [BEAM-147] Prototype of Metrics API for J...
Date Thu, 29 Sep 2016 00:03:38 GMT
GitHub user bjchambers opened a pull request:

    [BEAM-147] Prototype of Metrics API for Java DirectRunner

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [*] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [*] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [*] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [*] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

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

    $ git pull metrics

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

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

    This closes #1024
commit 40961aa24468c810f5f3377620fe14bc7d40c55c
Author: bchambers <>
Date:   2016-09-20T19:44:39Z

    Initial prototype of Beam Metrics API
    This is labeled @Experimental since it is only supported by the Direct
    Runner and may change as it is implemented in other runners.
    Future work includes adding additional kinds of metrics and wiring them
    up to the various runners.

commit 0c73cf2f2fb73eb1d171c911c10b36f79d564899
Author: bchambers <>
Date:   2016-09-27T23:41:10Z

    squash! Prototype Distribution metrics


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 or file a JIRA ticket
with INFRA.

View raw message