## Which problem is this PR solving? - Towards https://github.com/jaegertracing/jaeger/issues/7089 ## Description of the changes - This PR copies the gRPC API definitions from `jaeger` to this repository. In a follow-up PR, the proto definitions will be removed from `jaeger` and will point to this repo instead. ## How was this change tested? - CI ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [x] I have added unit tests for the new functionality - [x] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `npm run lint` and `npm run test` --------- Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com> |
||
---|---|---|
.github/workflows | ||
internal/tools | ||
model/v1 | ||
opentelemetry-proto@4ca4f0335c | ||
proto | ||
proto-gen/api_v2 | ||
swagger | ||
thrift | ||
thrift-gen | ||
.codecov.yml | ||
.gitignore | ||
.gitmodules | ||
.golangci.yaml | ||
CONTRIBUTING.md | ||
DCO | ||
LICENSE | ||
Makefile | ||
README.md | ||
go.mod | ||
go.sum | ||
renovate.json |
README.md
jaeger-idl

A set of shared Thrift and Protobuf data model definitions used by the Jaeger components.
As of Jan 2025 this repository also hosts Go code:
- implementation of Jaeger-v1 domain model
- Previous import path
"github.com/jaegertracing/jaeger/model"
- New import part is
"github.com/jaegertracing/jaeger-idl/model/v1"
- Previous import path
protoc
-generated Go types forapi_v2
- Previous import path
"github.com/jaegertracing/jaeger/proto-gen/api_v2"
- New import part is
"github.com/jaegertracing/jaeger-idl/proto-gen/api_v2"
- Previous import path
- All Thrift-generated types
- Previous import path
"github.com/jaegertracing/jaeger/thrift-gen/{agent,jaeger,sampling,zipkincore}"
- New import part is
"github.com/jaegertracing/jaeger-idl/thrift-gen/..."
- Previous import path
Generating code
This repository only include Go code for some of the Thrift and Protobuf modules. It also runs Thrift and protoc
generators as part of the CI to verify all IDL files. See the Makefile for example. In particular, the classes for different languages can be compiled using the jaegertracing/protobuf
Docker image (see README).
To generate the stubs for your own purposes:
- clone the repository
- run
make proto-all
ormake thrift-all
- the stubs will be generated under
.thrift-gen-polyglot/gen-{lang}
for Thrift and.proto-gen-polyglot/{lang}
for Protobuf
Compatibility
The Jaeger repositories that use these IDL files usually import this repository as a Git submodule, so you can verify which revision of the IDLs is being used by looking at the submodule commit sha, e.g. in GitHub it will show like this [->] idl @ d64c4eb
.
Contributing
See CONTRIBUTING.