jaegertracing / jaeger-performance Goto Github PK

Requirement - what kind of business use case are you trying to solve?

Run Performance and smoke tests locally

Problem - what in Jaeger blocks you from solving the requirement?

Got the error:

Running io.jaegertracing.tests.run.SmokeTest
2020-11-09 15:31:18,845 ERROR [main] [io.jaegertracing.tests.clients.GenericRestClient:129] Exception,
java.net.ConnectException: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:8080

Same error from docker image jkandasa/jaeger-performance-test 3.1

Proposal - what do you suggest to solve the problem or improve the existing situation?

Add more instructions how to run local tests to readme

Any open questions to address

We often have to ask other people "could you please run your service with this new version of Jaeger library" before we feel confident publishing a new release that can be automatically picked up by other services.

There are different reasons why we perceive the risk of new release. One of them is potential performance impact - does the new version have a significant performance regression?

See jaegertracing/jaeger#771 (comment)

I've tried to add an exclude in the configuration section for the maven license plugin in the top level pom to ignore generated java classes in restclient/gen-java, but so far I have not been able to define it properly. In the meantime I have added "false" so it will report license violations but not fail the build.

Currently ValidateTracesTest.validateElasticSearchTraces() builds the url for counting traces in elasticsearch using the current date. This will fail if not work correctly if the test was started the previous day and has run past midnight.

In that case we need to do two queries (or possibly more if we're running for more than 1 day) and report the sum of those numbers.

There is no summary report like spans sent, found, drop percentage, etc.