使用JMeter测试SpringBoot应用：记录请求-响应配对日志方法

Hey Jeff, let me walk you through exactly how to set up JMeter to log paired request-response data for your Spring Boot app—since you’re new to JMeter, I’ll break this down step by step so you can easily check for response data crosstalk.

First, let’s get the core test structure in place:

• Open JMeter, right-click on Test Plan → Add → Threads (Users) → Thread Group. Configure the number of threads (your concurrency level) and loop times based on your testing needs.
• Right-click the Thread Group → Add → Sampler → HTTP Request. Fill in your Spring Boot app’s server IP/name, port, and endpoint path (like /api/your-target-endpoint).
• Set the request method to POST (since you’re sending JSON payloads). Switch to the Body Data tab and paste your JSON request body, e.g.:

  {
    "username": "test-user",
    "data": "sample-payload"
  }
  

• Don’t forget to add an HTTP Header Manager: Right-click Thread Group → Add → Config Element → HTTP Header Manager. Add a header with Name: Content-Type and Value: application/json—this tells your Spring Boot app you’re sending JSON.

To reliably link each request to its response, we’ll generate a unique UUID for every request:

• Right-click Thread Group → Add → Pre Processors → JSR223 PreProcessor.
• Use Groovy (it’s the fastest scripting option in JMeter) and paste this code:

  def requestId = UUID.randomUUID().toString()
  vars.put("REQUEST_ID", requestId)
  log.info("Generated Request ID: ${requestId}")
  

This creates a unique ID before each request runs and stores it in a JMeter variable called REQUEST_ID.

You mentioned having issues with the Simple Writer—let’s cover both that tool (with correct setup) and a more flexible custom option.

Option 1: JSR223 Listener (Most Flexible) #

This lets you fully control what gets logged and how, so you’ll never lose track of which request matches which response:

• Right-click Thread Group → Add → Listener → JSR223 Listener.
• Paste this Groovy script into the Script box:

  def requestId = vars.get("REQUEST_ID")
  def requestBody = sampler.getArguments().getArgument(0).getValue()
  def responseBody = prev.getResponseDataAsString()
  def logFile = new File("request-response-pairs.log") // Change path as needed
  
  // Write formatted data to the log file
  logFile.append("=== Request-Response Pair [${requestId}] ===\n")
  logFile.append("Timestamp: ${new Date()}\n")
  logFile.append("Request Body:\n${requestBody}\n")
  logFile.append("Response Body:\n${responseBody}\n")
  logFile.append("----------------------------------------\n\n")
  

• Adjust the logFile path to where you want to store logs (e.g., "/Users/you/jmeter-logs/pairs.log" for macOS, "C:\jmeter-logs\pairs.log" for Windows).
• When you run the test, this will write every request’s ID, timestamp, payload, and matching response to a single file—each pair is separated by a divider for easy reading.

Option 2: Simple Data Writer (JMeter’s Built-In Tool) #

If you prefer using the tool you tried earlier, here’s the correct setup to log paired data:

• Right-click Thread Group → Add → Listener → Simple Data Writer.
• Enter a file path in the Filename field (e.g., simple-pairs.log).
• Click the Configure button:
  • Check Save Request Data and Save Response Data to capture both payloads.
  • To link requests and responses, switch to the Custom Fields tab, click Add, and enter REQUEST_ID in the Variable Name field. This ensures the unique ID is included with every log entry.
  • For JSON payloads, avoid CSV format (it can break with line breaks in JSON)—instead, select Save as XML so the data stays intact.

• Click the Start button in JMeter’s toolbar to run your test.
• After the test finishes, open your log file. You should see each request-response pair tied to the same REQUEST_ID. Search for a specific ID to quickly cross-check if the response matches the corresponding request—this lets you easily spot any data crosstalk.

• To make debugging even easier, add the REQUEST_ID as a request header: In the HTTP Header Manager, add Name: X-Request-ID and Value: ${REQUEST_ID}. This way, your Spring Boot app can log the same ID, letting you correlate JMeter logs with backend logs.
• If logs get too large, modify the JSR223 script to roll logs daily (e.g., include the date in the filename) or add logic to limit file size.
• Start with a single thread first to confirm logs work correctly, then ramp up to your desired concurrency level.

内容的提问来源于stack exchange，提问作者Jeff