Simple integration of Jaeger / Opentracing #32
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frouioui
added
enhancement
|
Here is an example of a trace going from the web client, to Traefik, then to the Frontend, then to the Articles API, and finally reaching Vitess cluster (more specifically vtgate, and then the multiple vttablets, since we have 2 shards). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR proposes a simple a integration of Jaeger in to tagenal. A new namespace
observabilitywas created and hosts the operator, the agent, and all the other required resources to run Jaeger.Jaeger is run using the
AllInOneconfiguration, as the purposes is solely for demo / experimentation.Tracing is implemented throughout the whole application. From Traefik to Vitess.
Is traced:
The propagation from the APIs to Vitess was achieved by adding a
DialOption(grpc.UnaryClientInterceptor) into theGRPCDialOptionsof thevitessdriver's configuration.A new service was created in the
vitesskeyspace, which aim to ease of development. We can now callvitess-zone1-vtgate-srvinstead of calling the pseudo-random-generated service name by Vitess operator.