update supported tracers (fix #216) (#372)

config.yaml

@@ -75,18 +75,9 @@ params:
   - name: Lightstep
     url: http://lightstep.com
     icon: lightstep.png
-  - name: Appdash
-    url: https://github.com/sourcegraph/appdash
-    icon: appdash.png
-  - name: Tracer
-    url: https://github.com/tracer/tracer
-    icon: false
   - name: Jaeger
     url: http://uber.github.io/jaeger/
     icon: false
-  - name: Hawkular
-    url: http://www.hawkular.org/hawkular-apm/
-    icon: hawkular.svg
   - name: Instana
     url: https://www.instana.com
     icon: instana.svg

content/docs/overview/inject-extract.md

@@ -11,7 +11,7 @@ This document provides a concise summary of the design and proper use of `Inject
 
 The hardest thing about distributed tracing is the *distributed* part. Any tracing system needs a way of understanding the causal relationship between activities in many distinct processes, whether they be connected via formal RPC frameworks, pub-sub systems, generic message queues, direct HTTP calls, best-effort UDP packets, or something else entirely.
 
-Some distributed tracing systems (e.g., [Project5](http://dl.acm.org/citation.cfm?id=945454) from 2003, or [WAP5](http://www.2006.org/programme/item.php?id=2033) from 2006 or [The Mystery Machine](https://www.usenix.org/node/186168) from 2014) *infer* causal relationships across process boundaries. Of course **there is a tradeoff between the apparent convenience of these black-box inference-based approaches and the freshness and quality of the assembled traces.** Per the concern about quality, OpenTracing is an *explicit* distributed tracing instrumentation standard, and as such it is much better-aligned with approaches like [X-Trace](https://www.usenix.org/conference/nsdi-07/x-trace-pervasive-network-tracing-framework) from 2007, [Dapper](http://research.google.com/pubs/pub36356.html) from 2010, or numerous open-source tracing systems like [Zipkin](https://github.com/openzipkin) or [Appdash](https://github.com/sourcegraph/appdash) (among others).
+Some distributed tracing systems (e.g., [Project5](http://dl.acm.org/citation.cfm?id=945454) from 2003, or [WAP5](http://www.2006.org/programme/item.php?id=2033) from 2006 or [The Mystery Machine](https://www.usenix.org/node/186168) from 2014) *infer* causal relationships across process boundaries. Of course **there is a tradeoff between the apparent convenience of these black-box inference-based approaches and the freshness and quality of the assembled traces.** Per the concern about quality, OpenTracing is an *explicit* distributed tracing instrumentation standard, and as such it is much better-aligned with approaches like [X-Trace](https://www.usenix.org/conference/nsdi-07/x-trace-pervasive-network-tracing-framework) from 2007, [Dapper](http://research.google.com/pubs/pub36356.html) from 2010, or numerous open-source tracing systems like [Zipkin](https://github.com/openzipkin) or [Jaeger](https://github.com/jaegertracing/jaeger) (among others).
 
 **Together, `Inject` and `Extract` allow for inter-process trace propagation without tightly coupling the programmer to a particular OpenTracing implementation.**
 

content/docs/supported-tracers.md

@@ -7,13 +7,6 @@ title: Supported tracers
 [Jaeger \\ˈyā-gər\\](https://jaegertracing.io) is a distributed tracing system, originally open sourced by [Uber Technologies](https://eng.uber.com/distributed-tracing/). It provides distributed context propagation, distributed transaction monitoring, root cause analysis, service dependency analysis, and performance / latency optimization. Built with OpenTracing support from inception, Jaeger includes OpenTracing client libraries in several languages, including [Java](https://github.com/jaegertracing/jaeger-client-java), [Go](https://github.com/jaegertracing/jaeger-client-go), [Python](https://github.com/jaegertracing/jaeger-client-python), [Node.js](https://github.com/jaegertracing/jaeger-client-node), [C++](https://github.com/jaegertracing/cpp-client) and [C#](https://github.com/jaegertracing/jaeger-client-csharp). It is a [Cloud Native Computing Foundation](https://www.cncf.io/) member project.
 
 
-## Appdash
-
-Appdash ([background reading](https://about.sourcegraph.com/blog/appdash-an-open-source-perf-tracing-suite/)) is a lightweight, Golang-based distributed tracing system, originally developed and since open-sourced by [sourcegraph](https://sourcegraph.com/). There is an OpenTracing-compatible `Tracer` implementation that uses Appdash as a backend.
-
-For more details, read [the godocs](https://godoc.org/github.com/sourcegraph/appdash/opentracing).
-
-
 ## LightStep
 
 [LightStep](http://lightstep.com/) operates a SaaS solution with OpenTracing-native tracers in production environments. There are OpenTracing-compatible [LightStep Tracers](https://github.com/lightstep) available for Go, Python, Javascript, Objective-C, Java, PHP, Ruby, and C++.

data/tracers.yaml

@@ -1,7 +1,3 @@
-- system: appdash
-  languages:
-  - language: Go
-    repo: https://github.com/sourcegraph/appdash
 - system: CNCF Jaeger
   languages:
   - language: Java

resources/_gen/assets/scss/scss/style.scss_fbbbc62c786286473d9c728ad0108593.json

@@ -1 +1 @@
-{"Target":"css/style.min.1d1f0aca96bbbf6eea750a7f6e9d5e9de9da93be4a2c0fa209d2d8e2b3ea056a.css","MediaType":"text/css","Data":{"Integrity":"sha256-HR8Kypa7v27qdQp/bp1enenak75KLA+iCdLY4rPqBWo="}}
+{"Target":"css/style.min.3995c554c5dbb94abf1eee44b087331f5b87bf16422e2f0dfcdaffa552986f22.css","MediaType":"text/css","Data":{"Integrity":"sha256-OZXFVMXbuUq/Hu5EsIczH1uHvxZCLi8N/Nr/pVKYbyI="}}

themes/tracer/assets/scss/_components/_logo-bar.scss

@@ -94,11 +94,6 @@ $logo-bar-scale: 14px;
           height: $logo-bar-scale + 8;
         }
 
-        &[src*="appdash.png"] {
-          margin-left: 15px;
-          max-height: $logo-bar-scale * 1.3;
-        }
-
         &[src*="finagle"] {
           max-height: $logo-bar-scale * 1.1;
         }
@@ -142,10 +137,6 @@ $logo-bar-scale: 14px;
             max-height: $logo-bar-scale * 0.6;
           }
 
-          &[src*="appdash.png"] {
-            max-height: $logo-bar-scale * 1.3;
-          }
-
           &[src*="finagle"] {
             max-height: $logo-bar-scale * 1.1;
           }