Skip to content
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.

Add readme for spinning up notebooks #53

Merged
merged 3 commits into from
Jul 11, 2024

Conversation

shreyagupta30
Copy link
Contributor

This fixes #51
I have added a readme file that provides instructions on how to spin up the jupyter notebooks for the Data Analytics.

cc: @jpkrohling

@fktkrt
Copy link

fktkrt commented Oct 26, 2020

I've wanted to compose a similar guide to this one, but got buried in another projects.
Anyway, please take a look at my PR #54 as it has a docker-compose solution, which can we used for this guide also, if you want to simply the process of setting these up.

If it makes sense, that can be merged, and this PR can be easily changed to use that compose.
What do you think?

Copy link
Member

@yurishkuro yurishkuro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • please add links to the main README
  • are the screenshots really critical/necessary? I feel like they can be safely omitted and text can describe what you want them to show.

@shreyagupta30
Copy link
Contributor Author

shreyagupta30 commented Oct 27, 2020

@yurishkuro Thanks for your feedback. I will make the required changes

@shreyagupta30
Copy link
Contributor Author

Hi @jpkrohling and @yurishkuro, I have made the requested changes in the readme. Kindly review it and let me know if any further changes are required.

1. For Jaeger UI:

``` bash
docker run --rm -it -p 16686:16686 --name=jaeger jaegertracing/all-in-one:1.17

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
docker run --rm -it -p 16686:16686 --name=jaeger jaegertracing/all-in-one:1.17
docker run --rm -it -p 16686:16686 --name=jaeger jaegertracing/all-in-one:1.20


*Note : Add `-v ${PWD}:/home/jovyan/work` to Jupyter notebook if you want to open the notebooks from your current directory.*

After succesfully running the docker script, you will be able to see a URL in you terminal with unique token. Paste that URL in your browser to start the jupyter notebook.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After succesfully running the docker script, you will be able to see a URL in you terminal with unique token. Paste that URL in your browser to start the jupyter notebook.
After successfully running the `docker` commands, you will be able to see a URL in you terminal with unique token. Paste that URL in your browser to start the Jupyter notebook.

For the analysis we have to generate some data, so in the HotROD UI click on the blue boxes to order a car that generates nice traces. To verify that the trace reached Jaeger open Jaeger UI and search for traces from the `frontend` service.
You'll be able to see the generated traces for the services and operation.

Once we know that the data is stored in Jaeger we can move to Jupyter notebook and load the trace there. Jaeger notebooks are stored in the jupyter directory. This directory can either be opened from the project root directory or from work in case the notebooks from host filesystem are injected into the docker container.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Once we know that the data is stored in Jaeger we can move to Jupyter notebook and load the trace there. Jaeger notebooks are stored in the jupyter directory. This directory can either be opened from the project root directory or from work in case the notebooks from host filesystem are injected into the docker container.
Once we know that the data is stored in Jaeger we can move to Jupyter notebook and load the trace there. Jaeger notebooks are stored in the jupyter directory. This directory can either be opened from the project root directory or from work in case the notebooks from host filesystem are injected into the container.

For the analysis we have to generate some data, so in the HotROD UI click on the blue boxes to order a car that generates nice traces. To verify that the trace reached Jaeger open Jaeger UI and search for traces from the `frontend` service.
You'll be able to see the generated traces for the services and operation.

Once we know that the data is stored in Jaeger we can move to Jupyter notebook and load the trace there. Jaeger notebooks are stored in the jupyter directory. This directory can either be opened from the project root directory or from work in case the notebooks from host filesystem are injected into the docker container.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does "load the trace there" mean? What are the steps? Which notebook should be opened?


Once we know that the data is stored in Jaeger we can move to Jupyter notebook and load the trace there. Jaeger notebooks are stored in the jupyter directory. This directory can either be opened from the project root directory or from work in case the notebooks from host filesystem are injected into the docker container.

Before running the analysis we have to load dependencies into the notebook’s classpath. Just click on the dependencies cell to make it active and then on the play icon in the top navigation menu.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, I get the errors you were having some time ago:

TraceTraversal<Vertex, Vertex> traversal = graph.traversal(TraceTraversalSource.class)
cannot find symbol
  symbol:   class TraceTraversal

Do you remember what was the problem?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, there were some missing dependencies in pom.xml file somewhere but I wasn't able to understand what was the exact problem.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a problem in the jaegertracing/jaeger-analytics-java project then? @pavolloffay do you know if there's something missing on our setup?

It should look something like:
``` java
String queryHostPort = "jaeger:16686";
String traceIdStr = "2cb1f0c274c3b4a5"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is this then used?

Signed-off-by: shreyagupta30 <[email protected]>
@shreyagupta30
Copy link
Contributor Author

Hi @jpkrohling, I have made the requested changes and it's ready for review. :)

@jpkrohling
Copy link

I'm unable to review it today, but will take a look soon.

Copy link

@jpkrohling jpkrohling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple of minor comments, but it's ready to be merged. @yurishkuro you left a comment earlier on this PR, would you like to take another look?


2. For HotROD demo application, run
``` bash
docker run --rm -it -p 8080:8080 --link=jaeger -e JAEGER_ENDPOINT=http://jaeger:14268/api/traces jaegertracing/example-hotrod:1.17

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This version should be the same as the all-in-one



``` bash
docker run --rm -it -p 8888:8888 -p 4041:4040 -p 9001:9001 --link=jaeger -e JUPYTER_ENABLE_LAB=yes quay.io/jaegertracing/jaeger-analytics-java:latest

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-p 4041:4040 -- is it a typo, or should one really be different than the other?

@yurishkuro yurishkuro merged commit 4e92b5a into jaegertracing:master Jul 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

README for Jupyter directory
4 participants