JessicaGreben/db-trace

## db-trace
From a production satellite:

1. Port forward from the pod
I=0; for API in $(kubectl -n satellite get pods | rg api | awk '{print $1}'); do I=$(($I+1)); kubectl -n satellite port-forward $API 5999$I:5999 & done

2. Hit the db trace debug endpoint
curl 127.0.0.1:5999{1,2,3}/debug/run/trace/db

3. Perform desired uplink operation, i.e. upload/download/etc

4. Copy the db traces out of the pods (will be in /tmp/storj-traces) to a local path
kubectl cp <podname>:/tmp/storj-traces <local/path>

5. Inspect the traces
There are filtered and unfiltered results. Unfiltered is the entire trace if that trace touched the db. Filtered is an svgs of things that only touched the db, less useful.
File name is in the format: RPC/funcHash/<durationInNS-timestampUnixNano>.[json|svg]
	From a production satellite:

	1. Port forward from the pod
	I=0; for API in $(kubectl -n satellite get pods \| rg api \| awk '{print $1}'); do I=$(($I+1)); kubectl -n satellite port-forward $API 5999$I:5999 & done

	2. Hit the db trace debug endpoint
	curl 127.0.0.1:5999{1,2,3}/debug/run/trace/db

	3. Perform desired uplink operation, i.e. upload/download/etc

	4. Copy the db traces out of the pods (will be in /tmp/storj-traces) to a local path
	kubectl cp <podname>:/tmp/storj-traces <local/path>

	5. Inspect the traces
	There are filtered and unfiltered results. Unfiltered is the entire trace if that trace touched the db. Filtered is an svgs of things that only touched the db, less useful.
	File name is in the format: RPC/funcHash/<durationInNS-timestampUnixNano>.[json\|svg]