如何从JMeter向InfluxDB推送迭代次数与用户编号

Absolutely! You can easily add iteration count and thread/user ID to the metrics you’re already pushing to InfluxDB. Here are two reliable, actionable methods to make this happen:

Method 1: Use JSR223 Elements to Set Custom Variables (No Code Compilation Needed) #

This is the quickest approach if you want to avoid modifying the existing backend listener client:

• Step 1: Add a JSR223 PostProcessor to your thread group (or directly under individual samplers if you need per-sampler iteration tracking).
• Step 2: Insert this Groovy script into the postprocessor to define the required variables:

  // Get human-readable iteration count (starts at 0 by default, so we add 1)
  def iterationCount = ctx.getThread().getIteration() + 1
  vars.put("iteration_count", iterationCount.toString())
  
  // Get unique thread ID (use thread name instead with ctx.getThread().getName() if preferred)
  def threadId = ctx.getThread().getThreadNum()
  vars.put("thread_id", threadId.toString())
  

• Step 3: Configure the InfluxdbBackendListenerClient to include these custom fields:
  1. In your backend listener settings, locate the "Custom Fields" section.
  2. Add entries in the format [influx_field_name]:[jmeter_variable_name], like:
     • iteration_count:iteration_count
     • thread_id:thread_id
  3. Save your test plan and run it. The new fields will now be included in every metric push to InfluxDB.

Method 2: Extend the InfluxdbBackendListenerClient Class (For Full Control) #

If you want a more integrated solution, create a custom backend listener by extending the default client:

• Step 1: Create a Java class that inherits from org.apache.jmeter.visualizers.backend.influxdb.InfluxdbBackendListenerClient.
• Step 2: Override the addCustomMetrics method to inject iteration count and thread ID directly:

  import org.apache.jmeter.samplers.SampleResult;
  import org.apache.jmeter.visualizers.backend.influxdb.InfluxdbBackendListenerClient;
  import org.apache.jmeter.visualizers.backend.influxdb.MetricCollector;
  
  public class CustomInfluxBackendListener extends InfluxdbBackendListenerClient {
      @Override
      protected void addCustomMetrics(SampleResult sampleResult, MetricCollector collector) {
          super.addCustomMetrics(sampleResult, collector);
          
          // Add iteration count (adjusted to start at 1)
          int iterationCount = sampleResult.getThreadContext().getThread().getIteration() + 1;
          collector.addMetric("iteration_count", iterationCount);
          
          // Add thread ID
          int threadId = sampleResult.getThreadContext().getThread().getThreadNum();
          collector.addMetric("thread_id", threadId);
      }
  }
  

• Step 3: Package the class into a JAR and place it in JMeter’s lib/ext directory.
• Step 4: Select your custom class in the backend listener’s "Backend Listener Implementation" dropdown instead of the default client.

Quick Verification Tips #

• After running your test, query InfluxDB to confirm the new fields exist:

  SELECT time, requestName, iteration_count, thread_id FROM "jmeter"."autogen"."requests" LIMIT 10
  

• Use JMeter’s View Results Tree listener (with the "Variables" tab) to check if iteration_count and thread_id are being set correctly during execution.

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