Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/sourcegraph/appdash

Application tracing system for Go, based on Google's Dapper.
https://github.com/sourcegraph/appdash

Last synced: about 1 month ago
JSON representation

Application tracing system for Go, based on Google's Dapper.

Awesome Lists containing this project

README 

        
# appdash (view on [Sourcegraph](https://sourcegraph.com/github.com/sourcegraph/appdash))



Appdash is an application tracing system for Go, based on

[Google's Dapper](http://research.google.com/pubs/pub36356.html) and

[Twitter's Zipkin](https://zipkin.io/).



Appdash allows you to trace the end-to-end handling of requests and

operations in your application (for perf and debugging). It displays

timings and application-specific metadata for each step, and it

displays a tree and timeline for each request and its children.



To use appdash, you must instrument your application with calls to an

appdash recorder. You can record any type of event or

operation. Recorders and schemas for HTTP (client and server) and SQL

are provided, and you can write your own.



## Usage



To install appdash, run:



```

go get -u sourcegraph.com/sourcegraph/appdash/cmd/...

```



A standalone example using Negroni and Gorilla packages is available in the `examples/cmd/webapp` folder.



A demo / pure `net/http` application (which is slightly more verbose) is also available at `cmd/appdash/example_app.go`, and it can be ran easily using `appdash demo` on the command line.



## Community



Questions or comments? Join us [on #sourcegraph](https://invite.slack.golangbridge.org/) in the Gophers slack!



## Development



Appdash uses [vfsgen](https://github.com/shurcooL/vfsgen) to package HTML templates with the appdash binary for

distribution. This means that if you want to modify the template data in `traceapp/tmpl` you can first build using the `dev` build tag, which makes the template data be reloaded from disk live.



After you're finished making changes to the templates, always run `go generate sourcegraph.com/sourcegraph/appdash/traceapp/tmpl` so that the `data_vfsdata.go` file is updated for normal Appdash users that aren't interested in modifying the template data.



## Components



Appdash follows the design and naming conventions of

[Google's Dapper](http://research.google.com/pubs/pub36356.html). You

should read that paper if you are curious about why certain

architectural choices were made.



There are 4 main components/concepts in appdash:



* [**Spans**](https://sourcegraph.com/sourcegraph.com/sourcegraph/appdash@master/.GoPackage/sourcegraph.com/sourcegraph/appdash/.def/SpanID):

  A span refers to an operation and all of its children. For example,

  an HTTP handler handles a request by calling other components in

  your system, which in turn make various API and DB calls. The HTTP

  handler's span includes all downstream operations and their

  descendents; likewise, each downstream operation is its own span and

  has its own descendents. In this way, appdash constructs a tree of

  all of the operations that occur during the handling of the HTTP

  request.

* [**Event**](https://sourcegraph.com/sourcegraph.com/sourcegraph/appdash@master/.GoPackage/sourcegraph.com/sourcegraph/appdash/.def/Event):

  Your application records the various operations it performs (in the

  course of handling a request) as Events. Events can be arbitrary

  messages or metadata, or they can be structured event types defined

  by a Go type (such as an HTTP

  [ServerEvent](https://sourcegraph.com/sourcegraph.com/sourcegraph/appdash@master/.GoPackage/sourcegraph.com/sourcegraph/appdash/httptrace/.def/ServerEvent)

  or an

  [SQLEvent](https://sourcegraph.com/sourcegraph.com/sourcegraph/appdash@master/.GoPackage/sourcegraph.com/sourcegraph/appdash/sqltrace/.def/SQLEvent)).

* [**Recorder**](https://sourcegraph.com/sourcegraph.com/sourcegraph/appdash@master/.GoPackage/sourcegraph.com/sourcegraph/appdash/.def/Recorder):

  Your application uses a Recorder to send events to a Collector (see

  below). Each Recorder is associated with a particular span in the

  tree of operations that are handling a particular request, and all

  events sent via a Recorder are automatically associated with that

  context.

* [**Collector**](https://sourcegraph.com/sourcegraph.com/sourcegraph/appdash@master/.GoPackage/sourcegraph.com/sourcegraph/appdash/.def/Collector):

  A Collector receives Annotations (which are the encoded form of

  Events) sent by a Recorder. Typically, your application's Recorder

  talks to a local Collector (created with

  [NewRemoteCollector](https://sourcegraph.com/sourcegraph.com/sourcegraph/appdash@master/.GoPackage/sourcegraph.com/sourcegraph/appdash/.def/NewRemoteCollector). This

  local Collector forwards data to a remote appdash server (created

  with

  [NewServer](https://sourcegraph.com/sourcegraph.com/sourcegraph/appdash@master/.GoPackage/sourcegraph.com/sourcegraph/appdash/.def/NewServer)

  that combines traces from all of the services that compose your

  application. The appdash server in turn runs a Collector that

  listens on the network for this data, and it then stores what it

  receives.



## Language Support



Appdash has clients available for Go, Python (see `python/` subdir) and Ruby (see https://github.com/bsm/appdash-rb).



## OpenTracing Support



Appdash supports the [OpenTracing](http://opentracing.io) API. Please see the

`opentracing` subdir for the Go implementation, or see [the GoDoc](https://godoc.org/sourcegraph.com/sourcegraph/appdash/opentracing)

for API documentation.



## Acknowledgments



**appdash** was influenced by, and uses code from, Coda Hale's

[lunk](https://github.com/codahale/lunk).