You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -9,43 +9,44 @@ A JMeter plug-in that enables you to send test results to a Kafka server.
9
9
# Overview
10
10
11
11
### Description
12
+
12
13
JMeter Backend Listener Kafka is a JMeter plugin enabling you to send test results to a Kafka server.
13
14
It is inspired from JMeter [ElasticSearch](https://github.com/delirius325/jmeter-elasticsearch-backend-listener) backend listener plug-in.
14
15
15
16
### Features
16
17
17
-
* Filters
18
-
*Only send the samples you want, by using Filters! Simply type them as follows in the appropriate field: ``filter1;filter2;filter3`` or ``sampleLabel_must_contain_this``.
19
-
* Specific fields `field1;field2;field3`
20
-
* Specify fields that you want to send to Kafka (possible fields below):
21
-
* AllThreads
22
-
* BodySize
23
-
* Bytes
24
-
* SentBytes
25
-
* ConnectTime
26
-
* ContentType
27
-
* DataType
28
-
* ErrorCount
29
-
* GrpThreads
30
-
* IdleTime
31
-
* Latency
32
-
* ResponseTime
33
-
* SampleCount
34
-
* SampleLabel
35
-
* ThreadName
36
-
* URL
37
-
* ResponseCode
38
-
* TestStartTime
39
-
* SampleStartTime
40
-
* SampleEndTime
41
-
* Timestamp
42
-
* InjectorHostname
43
-
* Verbose, semi-verbose, error only, and quiet mode:
44
-
*__debug__ : Send request/response information of all samplers (headers, body, etc.)
45
-
*__info__ : Sends all samplers to the Kafka server, but only sends the headers, body info for the failed samplers.
46
-
*__quiet__ : Only sends the response time, bytes, and other metrics
47
-
*__error__ : Only sends the failing samplers to the Kafka server (Along with their headers and body information).
48
-
* Use Logstash/NiFi or any other tool to consume data from Kafka topic and then ingest it into a Database of your liking.
18
+
- Filters
19
+
-Only send the samples you want, by using Filters! Simply type them as follows in the appropriate field: `filter1;filter2;filter3` or `sampleLabel_must_contain_this`.
20
+
- Specific fields `field1;field2;field3`
21
+
- Specify fields that you want to send to Kafka (possible fields below):
22
+
- AllThreads
23
+
- BodySize
24
+
- Bytes
25
+
- SentBytes
26
+
- ConnectTime
27
+
- ContentType
28
+
- DataType
29
+
- ErrorCount
30
+
- GrpThreads
31
+
- IdleTime
32
+
- Latency
33
+
- ResponseTime
34
+
- SampleCount
35
+
- SampleLabel
36
+
- ThreadName
37
+
- URL
38
+
- ResponseCode
39
+
- TestStartTime
40
+
- SampleStartTime
41
+
- SampleEndTime
42
+
- Timestamp
43
+
- InjectorHostname
44
+
- Verbose, semi-verbose, error only, and quiet mode:
45
+
-**debug** : Send request/response information of all samplers (headers, body, etc.)
46
+
-**info** : Sends all samplers to the Kafka server, but only sends the headers, body info for the failed samplers.
47
+
-**quiet** : Only sends the response time, bytes, and other metrics
48
+
-**error** : Only sends the failing samplers to the Kafka server (Along with their headers and body information).
49
+
- Use Logstash/NiFi or any other tool to consume data from Kafka topic and then ingest it into a Database of your liking.
49
50
50
51
### Maven dependency
51
52
@@ -59,61 +60,63 @@ It is inspired from JMeter [ElasticSearch](https://github.com/delirius325/jmeter
59
60
60
61
### Installing JMeter
61
62
62
-
- SSH to a Unix machine with X-11 Forwarding enabled, and then set DISPLAY variable:
63
+
- SSH to a Unix machine with X-11 Forwarding enabled, and then set DISPLAY variable:
64
+
65
+
```bash
66
+
export DISPLAY=Your_terminal_IP:0.0
67
+
```
63
68
64
-
```bash
65
-
export DISPLAY=Your_terminal_IP:0.0
66
-
```
69
+
- Download [JMeter](https://jmeter.apache.org/download_jmeter.cgi) binary and extract it:
67
70
68
-
- Download [JMeter](https://jmeter.apache.org/download_jmeter.cgi) binary and extract it:
- In your **Test Pan**, right click on **Thread Group** > Add > Listener > Backend Listener
116
-
- Specify parameters as shown in image below (**bootstrap.servers** and **kafka.topic** are mandatory ones):
118
+
- In your **Test Pan**, right click on **Thread Group**> Add > Listener > Backend Listener
119
+
- Specify parameters as shown in image below (**bootstrap.servers** and **kafka.topic** are mandatory ones):
117
120
118
121

119
122
@@ -133,14 +136,36 @@ Feel free to contribute by branching and making pull requests, or simply by sugg
133
136
134
137
### Code Styling
135
138
136
-
- Please find instructions [here](https://github.com/HPI-Information-Systems/Metanome/wiki/Installing-the-google-styleguide-settings-in-intellij-and-eclipse) on how to configure your IntelliJ or Eclipse to format the source code according to Google style.
137
-
Once configured in IntelliJ, format code as normal with `Ctrl + Alt + L`.
138
-
139
-
Adding the XML file alone and auto-formatting the whole document could replace imports with wildcard imports, which isn't always what we want.
140
-
141
-
- To stop this from happening, Go to `File` → `Settings` → `Editor` → `Code Style` → `Java` and select the `Imports` tab.
142
-
- Set `Class Count to use import with '*'` and `Names count to us static import with '*'` to a higher value; anything over `999` should be fine.
143
-
144
-
You can now reformat code throughout your project without imports being changed to Wildcard imports.
145
-
146
-
- You also need to use `maven-git-code-format` plugin in `pom.xml` to auto format the code according to Google code style before any Git commit.
139
+
- Please find instructions [here](https://github.com/HPI-Information-Systems/Metanome/wiki/Installing-the-google-styleguide-settings-in-intellij-and-eclipse) on how to configure your IntelliJ or Eclipse to format the source code according to Google style.
140
+
Once configured in IntelliJ, format code as normal with `Ctrl + Alt + L`.
141
+
142
+
Adding the XML file alone and auto-formatting the whole document could replace imports with wildcard imports, which isn't always what we want.
143
+
144
+
- To stop this from happening, Go to `File` → `Settings` → `Editor` → `Code Style` → `Java` and selectthe`Imports` tab.
145
+
- Set `Class Count to use import with '*'` and `Names count to us static import with '*'` to a higher value; anything over `999` should be fine.
146
+
147
+
You can now reformat code throughout your project without imports being changed to Wildcard imports.
148
+
149
+
- You also need to use `maven-git-code-format` plugin in`pom.xml` to auto format the code according to Google code style before any Git commit.
It ensures a single style is used: list items use one type of bullet (_, -, +), emphasis (_ or \_) and importance (\_\_ or \*\*) use a standard marker, table fences are aligned, and more.
155
+
156
+
- Install `remark-cli` and `remark-preset-lint-recommended`
"description": "Apache JMeter plugin for sending sample results to a Kafka server. <ul><li>Simply add a \"Backend Listener\" and change the implementation</li><li>Change the listener's configuration</li><li>To use filters, simply separate their name by a semicolon. (f1;f2;f3)</li></ul>",
"description": "Apache JMeter plugin for sending sample results to a Kafka server. <ul><li>Simply add a \"Backend Listener\" and change the implementation</li><li>Change the listener's configuration</li><li>To use filters, simply separate their name by a semicolon. (f1;f2;f3)</li></ul>",
0 commit comments