This stress test example emulates the traces that a typical HTTP server with a SQL server dependency would generate.
It generates a fair amount of attributes, in order to give the generated spans some size.
The amount of traces generated is controlled by the NUM_ROOT_SPANS environment variable.
WARNING: Please notice at large NUM_ROOT_SPANS settings, this can incur real costs at your application insights resource - so be cautious!
When generating a large number of traces the batch span processor might start falling behind.
The user can mitigate this by configuring the batch span processor using the standard OpenTelemetry Environment Variable Specification settings.
Once #47 has been merged - perhaps we can update this example with another environment variable that controls if the stress test should use gzip compression or not?
See #46
This stress test example emulates the traces that a typical HTTP server with a SQL server dependency would generate. It generates a fair amount of attributes, in order to give the generated spans some size.
The amount of traces generated is controlled by the NUM_ROOT_SPANS environment variable.
WARNING: Please notice at large NUM_ROOT_SPANS settings, this can incur real costs at your application insights resource - so be cautious!
When generating a large number of traces the batch span processor might start falling behind. The user can mitigate this by configuring the batch span processor using the standard OpenTelemetry Environment Variable Specification settings.
Once #47 has been merged - perhaps we can update this example with another environment variable that controls if the stress test should use gzip compression or not?