Track DevOps story

[codefromthecrypt]

Currently, you can find out about zipkin's production story by watching presentations or asking on gitter. You'd find out status on docker, kubernetes, cloud foundry, prometheus, amazon, google and other approaches to managing zipkin. I think this is too effortful, and new users should be able to understand where things are easily, even if they are not in OpenZipkin repository.

This could be broken down into deploy telemetry and things like proxies (linkerd etc) as well production approaches. Scope is something interesting to consider.

Here are some links that need to be organized:
Zipkin Server's README - the readme has lots of info including prometheus and other monitoring details
Docker Zipkin - Docker files for zipkin with cassandra, uses pre-built jars
Kubernetes Zipkin - lets you start a k8 pod with zipkin components
Bosh Zipkin - Cloud Foundry BOSH release for zipkin with redis or cassandra backends.
Zipkin Interrogator - Analysis tool for sifting through traces
Swagger Zipkin - Wraps swagger http calls so that they carry trace identifiers
Zipkin-mesos-framework - scheduler for running zipkin components in mesos
Zipkin beanstalk - deploys zipkin using Amazon Elastic Beanstalk
Zipkin AWS Elasticsearch - use hosted elastic search instead of running your own
Google Stackdriver Trace Connector - You can use Google Stackdriver Trace as an alternate backend for Zipkin, although the data conversion is a little lossy.
latency histogram script - hdr histogram golang script @nicolai86 made to aggregate zipkin latency into elasticsearch

[codefromthecrypt]

cc @openzipkin/devops-tooling

[jasonrichardsmith]

K8s Deployment

Cloudformation for same stack