# Testing and benchmarking log collection pipeline

**URL:** https://discuss.elastic.co/t/testing-and-benchmarking-log-collection-pipeline/42942
**Category:** Logstash
**Created:** [February 28, 2016, 10:14am UTC](https://discuss.elastic.co/t/testing-and-benchmarking-log-collection-pipeline/42942 "2016-02-28T10:14:42Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![gaspaio](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gaspaio/32/8142_2.png) [@gaspaio](https://discuss.elastic.co/u/gaspaio)
#### Post date: [February 28, 2016, 10:14am UTC](https://discuss.elastic.co/t/testing-and-benchmarking-log-collection-pipeline/42942/1 "2016-02-28T10:14:42Z")

</div>

I'm looking for tools, or a set of tools, to test and benchmark logstash+kafka+ES setups :

- define test cases (log types, throughputs)
- maintain a base of log examples
- generate inputs for logstash at a given rate from the example files (some like [https://www.snmpsoft.com/cmd-tools/syslog-gen/](https://www.snmpsoft.com/cmd-tools/syslog-gen/))
- reproduce results with minimal humain vérification

Does something like a standard toolset exist to do thing sort of thing ?

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [February 28, 2016, 11:05am UTC](https://discuss.elastic.co/t/testing-and-benchmarking-log-collection-pipeline/42942/2 "2016-02-28T11:05:12Z")

</div>

I think Elastic have a bunch of performance test suites somewhere, but other than that I haven't heard of the kind of end-to-end testing tools that you describe. However, for testing Logstash filters specifically I think my own tool [Logstash Filter Verifier](https://github.com/magnusbaeck/logstash-filter-verifier) is useful. Verifying that filters are working as expected is probably easier done on the unit level than on the system level.

---

<div class="post-metadata">

### Author: ![gaspaio](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gaspaio/32/8142_2.png) [@gaspaio](https://discuss.elastic.co/u/gaspaio)
#### Post date: [February 29, 2016, 7:58am UTC](https://discuss.elastic.co/t/testing-and-benchmarking-log-collection-pipeline/42942/3 "2016-02-29T07:58:58Z")

</div>

Thanks Magnus,

I agree with you on unittesting your filters and patterns. I actually build  
a tool similar to yours (a lot simpler, using rspec) that allows you to  
define test cases for patterns, as well as filters: Logstash Tester  
[https://github.com/gaspaio/logstash-tester](https://github.com/gaspaio/logstash-tester).

I think an end to end testing suite would be really useful, for those cases  
when you have a defined set of logs that gets parsed, indexed and triggers  
some some of app behavior, and you want to test the whole chain and  
reproduce behaviros. Oh well, i'll probably end up hacking something myself  
for this.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 5:09am UTC](https://discuss.elastic.co/t/testing-and-benchmarking-log-collection-pipeline/42942/4 "2017-07-06T05:09:24Z")

</div>


