If an anchor with a span id is present in the traces URL, automatically pop up the modal with annotation details for that span.
Support for analyzing traces.

A trace analyzer that fetches traces from Zipkin query and looks for code problems.
The three initial problems are N+1 selects, N+1 service calls and service calls while a DB transactions is open.
The results of the analysis are stored. Initial storage implementation is a toy one - the file system. Using Cassandra is the likely next step.
A reporter looks at the results produced by the analyser and can create a text report that it publishes to a file. It supports reporting on all code problems
or just new code problems that haven't been reported before. The report has links back to Zipkin Web withc open up the trace/span where the problem was found.