New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace Zipkin with Jaeger #94
Closed
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
gkwan-ibm
requested changes
May 22, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- resolve the branch conflicts
- What you’ll learn
- Need to explain what is Jaeger in
- because using docker, need an additional prereq section
- Getting started
- Better to have a subsection to start Jaeger after the following line:
- "The finish directory contains the finished project that you will build."
- move the following statemnts to "What you’ll learn"
- "For this guide, use Jaeger as your distributed tracing system."
- "You can find more information about Jaeger in their Getting Started docs."
- dup "Try what you’ll build"
- I don't think
mvn liberty:start -pl system,inventory
will work. Need to runmvn liberty:run -pl system
andmvn liberty:start -pl inventory
by 2 different shells - change liberty-maven-plugin to 3.2.1
- need add more instructions how to get the spans. i.e. select
inventory
service, click theFind Traces
button, etc - instuctions to stop inventory and system services
- Better to have a subsection to start Jaeger after the following line:
- Existing Tracer implementation TODO
-
pom.xml
better hotspot the specific lines for jagaer/opentracing, even need rewrite this paragraph, i.e. "This feature" means what?-
server.xml
better hotspot the specific lines for jagaer/opentracing
-
- need to explain
<classloader apiTypeVisibility="+third-party"/>
? - the doc link "Enabling distributed tracing" is not good anymore. Ask Felix any better doc link. I doubt no need for this statemment because no need to install
usr:opentracingZipkin-0.31
-
- Enabling distributed tracing
- Enabling distributed tracing without code instrumentation
- "Both of these features are already enabled ..." not right now, remove and combine to the above paragraph
- Enabling explicit distributed tracing
- dev mode, no need to run
mvn compile
, there some places still have it - "...and sort the traces by newest first. " not clear enough what to do
-
get:io.openliberty.guides.inventory.inventoryresource.listcontents
andinventorymanager.list
not same as what I saw in the jagaer server. Make sure to update all outputs:GET:io.openliberty.guides.inventory.InventoryResource.listContents
InventoryManager.list
- "Again, run the mvn compile ..." no need to compile
- dev mode, no need to run
- Enabling distributed tracing without code instrumentation
- Testing the services
- need instruction to stop inventory, system services and jagaer server
|
|
|
* screenshots for span * new images for trace details
47 tasks
* linux peer review * mac peer review * slf4j dependencies * OS tabs for docker line breaks
…acing into jaeger # Conflicts: # README.adoc
This PR was addressed by the new guide https://openliberty.io/guides/microprofile-opentracing-jaeger.html |
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.
No description provided.