fix: start trace exporter only if required#8147
Conversation
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Proof generationEach column represents the number of threads used in proof generation.
L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 8 txs.
Circuits statsStats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.
Stats on running time collected for app circuits
AVM SimulationTime to simulate various public functions in the AVM.
Public DB AccessTime to access various public DBs.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contract classes are registered in the tx.
Transaction size based on fee payment method | Metric | | |
42c791d to
0a84cbf
Compare
|
|
0a84cbf to
0f75d29
Compare
This PR splits the collector URL into `_METRICS_ENDPOINT` and `_TRACES_ENDPOINT` and makes exporting traces optional (if no processor is registered then the default processor is a no-op) See https://www.npmjs.com/package/@opentelemetry/exporter-trace-otlp-http#user-content-configuration-options-as-environment-variables
This PR splits the collector URL into
_METRICS_ENDPOINTand_TRACES_ENDPOINTand makes exporting traces optional (if no processor is registered then the default processor is a no-op)See https://www.npmjs.com/package/@opentelemetry/exporter-trace-otlp-http#user-content-configuration-options-as-environment-variables