GitHub user cestella opened a pull request:

    https://github.com/apache/metron/pull/958

    METRON-1483: In performance evaluation, generating synthetic load and 
monitoring the write throughput of our kafka-to-kafka topologies has required a 
lot of custom scripting.  We should have a tool that could do the following:  
Take a file representing a message template and generate synthetic load at a 
given events per second Monitor the kafka offsets of a topic and report 
throughput numbers in events per second

    ## Contributor Comments
    In performance evaluation, generating synthetic load and monitoring the 
write throughput of our kafka-to-kafka topologies has required a lot of custom 
scripting.  We should have a tool that could do the following:
    
    * Take a file representing a message template and generate synthetic load 
at a given events per second
    * Monitor the kafka offsets of a topic and report throughput numbers in 
events per second
    
    Currently pending:
    * Test plan pending
    * Documentation
    
    ## Pull Request Checklist
    
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development 
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
 for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification 
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
 for complete smoke testing guides.  
    
    
    In order to streamline the review of the contribution we ask you follow 
these guidelines and ask you to double check the following:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
    - [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
    
    
    ### For code changes:
    - [x] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
    - [ ] Have you included steps or a guide to how the change may be verified 
and tested manually?
    - [x] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
      ```
      mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
      ```
    
    - [x] Have you written or updated unit tests and or integration tests to 
verify your changes?
    - [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
    - [x] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered by building and verifying the site-book? If not then run 
the following commands and the verify changes via 
`site-book/target/site/index.html`:
    
      ```
      cd site-book
      mvn site
      ```
    
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci](https://travis-ci.org) is set up 
for your personal repository such that your branches are built there before 
submitting a pull request.


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

    $ git pull https://github.com/cestella/incubator-metron perf_tool

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

    https://github.com/apache/metron/pull/958.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 #958
    
----
commit 8ba8c57576ed318d1ff3f69cda1dc9020d62352a
Author: cstella <cestella@...>
Date:   2018-03-08T00:03:33Z

    Build load testing tool

commit 638086f2f30cfe543b624721c1fb467062571eab
Author: cstella <cestella@...>
Date:   2018-03-08T15:31:55Z

    refactoring monitoring to be more sensible.

commit 55be01de033d0ea6b489930cb97fefcca80efdb5
Author: cstella <cestella@...>
Date:   2018-03-08T16:20:52Z

    Added summarization

----


---

Reply via email to