CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2413 Commits
44 Branches
214 Tags
188 MiB
 
 
Tag: Branch: Tree: a01b588a12
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a01b588a12'
${ noResults }
besu/docs/tracing
History
Antoine Toulme dbc3fee7bb
Add tracing agent to the build and default parameters in Dockerfiles (#1410) 		4 years ago
..
README.md Add tracing agent to the build and default parameters in Dockerfiles (#1410) 4 years ago
docker-compose.yml Add tracing agent to the build and default parameters in Dockerfiles (#1410) 4 years ago
otel-collector-config.yml Add tracing agent to the build and default parameters in Dockerfiles (#1410) 4 years ago

README.md

Tracing

Hyperledger Besu integrates with the open-telemetry project to integrate tracing reporting.

This allows to report all JSON-RPC traffic as traces.

To try out this example, start the Open Telemetry Collector and the Zipkin service with:

$> docker-compose up

Start besu with:

$> ./gradlew run --args="--network=dev --rpc-http-enabled"

Try interacting with the JSON-RPC API. Here is a simple example using cURL:

$> curl -X POST --data '{"jsonrpc":"2.0","method":"web3_clientVersion","params":[],"id":53}' http://localhost:8545

Open the Zipkin UI by browsing to http://localhost:9411/

You will be able to see the detail of your traces.