edgexfoundry / performance-test

Owner: QA-Testing WG
4 stars 9 forks source link

Core logging2 #18

Closed Walt-Intel closed 5 years ago

Walt-Intel commented 5 years ago

Initial check-in of core logging performance test.

cherrycl commented 5 years ago

@Walt-Intel I have the following questions/comments.

  1. Please remove "Property File Reader" which is only for developing. JMeter container which is used for automation doesn't install related the plugin.
  2. What is that purpose to add all of testplans in one jmx file? Is this a standalone testcase?
  3. If add the loglevel are required, what kind of logs you want to collect? I am thinking of the position of set log request.
cloudxxx8 commented 5 years ago

logging should be named support-logging

Walt-Intel commented 5 years ago

@Walt-Intel I have the following questions/comments.

  1. Please remove "Property File Reader" which is only for developing. JMeter container which is used for automation doesn't install related the plugin.

Ok, I will update the test to remove the file reader.

  1. What is that purpose to add all of testplans in one jmx file? Is this a standalone testcase?

I was planning on running the same test over a series of log level changes. My hope was to see a stair step in resource usage in Grafana.

  1. If add the loglevel are required, what kind of logs you want to collect? I am thinking of the position of set log request.

I want to set the log level in Consul in-between each iteration of the tests. Right now the test case goes from setting the level to DEBUG, TRACE and then INFO