{"action":"opened","issue":{"url":"https://api.github.com/repos/openzipkin/docker-zipkin/issues/101","repository_url":"https://api.github.com/repos/openzipkin/docker-zipkin","labels_url":"https://api.github.com/repos/openzipkin/docker-zipkin/issues/101/labels{/name}","comments_url":"https://api.github.com/repos/openzipkin/docker-zipkin/issues/101/comments","events_url":"https://api.github.com/repos/openzipkin/docker-zipkin/issues/101/events","html_url":"https://github.com/openzipkin/docker-zipkin/issues/101","id":161569664,"number":101,"title":"Add spigo instructions","user":{"login":"adriancole","id":64215,"avatar_url":"https://avatars.githubusercontent.com/u/64215?v=3","gravatar_id":"","url":"https://api.github.com/users/adriancole","html_url":"https://github.com/adriancole","followers_url":"https://api.github.com/users/adriancole/followers","following_url":"https://api.github.com/users/adriancole/following{/other_user}","gists_url":"https://api.github.com/users/adriancole/gists{/gist_id}","starred_url":"https://api.github.com/users/adriancole/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adriancole/subscriptions","organizations_url":"https://api.github.com/users/adriancole/orgs","repos_url":"https://api.github.com/users/adriancole/repos","events_url":"https://api.github.com/users/adriancole/events{/privacy}","received_events_url":"https://api.github.com/users/adriancole/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-22T00:28:20Z","updated_at":"2016-06-22T00:28:20Z","closed_at":null,"body":"zipkin has self-tracing, which can generate pretty interesting stuff based on what zipkin is doing. Another option is to use spigo, which can simulate larger architectures.\r\n\r\nHere's something we might want to add to the readme or a wiki vs expecting people to harvest slides..\r\n\r\nhttp://www.slideshare.net/adriancockcroft/microservices-application-tracing-standards-and-simulators-adrians-at-oscon\r\n\r\nThe following works after you've run `docker-compose up`. We could probably contribute to spigo to smooth or lessen some of the steps below.\r\n```bash\r\n# get spigo\r\n$ git clone https://github.com/adrianco/spigo.git;cd spigo\r\n# build spigo\r\n$ sh build.sh\r\n# run netflix for 2 seconds\r\n$ ./spigo -a netflix -d 2 -c\r\n# post json_metrics/netflix_flow.json zipkin\r\n$ sh misc/zipkin.sh netflix\r\n```\r\n\r\nOne way to reduce steps is to make some script to rebase the timestamps of `json_metrics/netflix_flow.json` during the curl (in misc/zipkin.sh). Ex if we rebase the stamps to today, then someone can just use the files that exist vs generating new ones (via spigo).\r\n\r\nAnother option is to make spigo report directly as opposed to writing a file first. ex https://github.com/adrianco/spigo/issues/67"}}
{"actor":{"display_login":"adriancole"}}