gh-action-trace
| Crates.io | gh-action-trace |
| lib.rs | gh-action-trace |
| version | 0.2.0 |
| source | src |
| created_at | 2021-11-25 06:00:03.845761 |
| updated_at | 2021-12-13 17:54:08.316917 |
| description | gh-action-trace is a CLI to create traces for GitHub Action runs by retrieving Action runs metadata from the GitHub API |
| homepage | |
| repository | https://github.com/Pothulapati/gh-action-trace |
| max_upload_size | |
| id | 487442 |
| size | 59,626 |
Tarun Pothulapati (Pothulapati)
documentation
README
gh-action-trace
gh-action-trace is a binary that can be used to generate traces
for GitHub Action runs by retrieving the metadata from GitHub
API.
Installation
cargo install gh-action-trace
Usage
First, Run jaeger locally to collect the traces.
docker run -d -p6831:6831/udp -p6832:6832/udp -p16686:16686 jaegertracing/all-in-one:latest --log-level debug
Now, Run the binary to generate and send the traces to Jaeger. Though, The
binary should work without a GitHub token, It is recommended to pass
a GitHub token through the --token flag for the binary to not be rate-limited.
$ gh-action-trace --owner linkerd --repo linkerd2 --runs 100 --token <GITHUB_TOKEN>
Completed workflow CI 10/10 [========================================] (0s)
Completed workflow Coverage 10/10 [========================================] (0s)
Completed workflow CodeQL 10/10 [========================================] (0s)
Completed workflow Integration tests 10/10 [========================================] (0s)
Completed workflow KinD integration 10/10 [========================================] (0s)
Completed workflow Lock Threads 10/10 [========================================] (0s)
Completed workflow Policy Controller 10/10 [========================================] (0s)
Completed workflow Release 10/10 [========================================] (0s)
Completed workflow Static checks 10/10 [========================================] (0s)
Completed workflow Unit tests 10/10 [========================================] (0s)
Completed workflow CI 10/10 [========================================] (0s)
You should be able to see traces in the Jaeger UI. :)