0b66d22be4
We do regular testing with executing uplink. But sometimes the recorded execution time showed spikes. Would be nice to know the reason of the spikes (just internet blip, or something what we should be worried about). We can collect distributed traces, but it's not easy to find the right trace in Jaeger. * We can provide a random trace-id, but it should be persisted / processed * We can also save standard output and use `--trace-verbose` which prints out the used trace id, but it's also complicated to collect all of them in a DB Would be nice to attach additional metadata to traces to make sure that we can filter all traces of one specific kind of test. This patch provides this feature: * It always adds hostname to the trace (if you opt-in to distributed tracing, which is turned off by default) * Additional tags can be defined with CLI flag Tags can be used to find the right trace in Jaeger (or in Elastic search backend of Jaeger). Change-Id: I08f10023bbebd783f812cfca95ac6237360ac2b0 |
||
|---|---|---|
| .. | ||
| certificates | ||
| crashcollect | ||
| identity | ||
| inspector | ||
| internal/wizard | ||
| metric-receiver | ||
| multinode | ||
| satellite | ||
| storagenode | ||
| storagenode-updater | ||
| storj-admin | ||
| storj-sim | ||
| tools | ||
| uplink | ||
| versioncontrol | ||