Cleanup of otter with a community focus. Because multiple otters build a damn a lot faster!
Otters is
- up to 10x faster when filtering spans
- up to 20x faster encoding data to send it
- using an easy to use filtering language
- including less invasive dependencies
- Dialyzer 'clean'
- Proactive im merging community contributes
- using EQC tests for higher test coverage
- using Elvis listing for code style
- providing a cleaner API
- more riddled with typos in the docs
OpenTracing Toolkit for Erlang
Instrumentation should have minimal impact on production code, so otters is tuned to be fast. So a few back of the envelop numbers (YMMV):
- filtering a span (using the filter language): < 1 microsecond (~3-10x improvement)
- encoding 1 spawn to be send: < 10 microseconds (~400x improvement)
OTTER uses rebar3 as build tool. It can be built with:
rebar3 compile
However most likely you'll want to add it to your project in your build environment.
ibrowse HTTP client is used to send the HTTP/Thrift requests to Zipkin.
OpenTracing is an open initiative to provide a set of terms and methods to produce, collect and correlate trace information in a distributed environment across different programming languages, platforms and protocols.
The concept defined for trace production is based on a span which is essentially a record of a handling in one environment. A span has a timestamp of when it started, a duration, a list of timestamped events marking the timing of important actions during the span and a list of key-value tags storing the parameters of the handled request (e.g. customer ids, transaction ids, results of subsequent actions). The span also contains id's to aid their correlation. The trace_id is used for correlating spans related to the handling of one request received from different systems. The trace_id is generated in the first system which starts handling a request (e.g. a frontend) and supposed to be passed on to other systems involved in the processing the same request. This is fairly simple when the protocols are fully under control and extensible (e.g. HTTP). Other id's recorded are the span_id and a parent_id referring to the parent span to help showing a hierarchical relationship of the spans in the trace collector.
After collecting this information, the span can be sent to a trace collector, which based on the id's of the received spans can correlate them and provide and end-to-end view of the request. Sending all produced spans could generate significant additional load on the system that produces them and also on the trace collector. It is recommended to filter the the spans before sending them to the collector.
The most mature trace collector at the time of the initial development is OpenZipkin. OTTER provides an interface to send spans to Zipkin using the HTTP/Thrift binary protocol.
The OpenTracing terminology defines information to be passed on across systems. The feasibility of this in most cases depends on the protocols used, and sometimes rather difficult to achieve. OTTER is not attempting to implement any of this functionality. It is possible though to initialize a span in OTTER with a trace_id and parent_id, but how these id's are passed across the systems is left to the particular implementation.
OTTER helps producing span information, filtering spans, sending to trace collector (Zipkin) and also counting and keeping a snapshot of the last occurrence of a span.
The main motivation behind the span collection of Otter is to make the instrumentation of existing code as simple as possible.
The following type specifications are in otter.hrl
-type time_us() :: integer(). % timestamp in microseconds
-type info() :: binary() | iolist() | atom() | integer().
-type ip4() :: {integer(), integer(), integer(), integer()}.
-type service() :: binary() | list() | default | {binary() | list(), ip4(), integer()}.
-type trace_id():: integer().
-type span_id() :: integer().
-record(span , {
timestamp :: time_us(), % timestamp of starting the span
trace_id :: trace_id(), % 64 bit integer trace id
name :: info(), % name of the span
id :: span_id(), % 64 bit integer span id
parent_id :: span_id() | undefined, % 64 bit integer parent span id
tags = [] :: [{info(), info()} | {info(), info(), service()}], % span tags
logs = [] :: [{time_us(), info()} | {info(), info(), service()}], % span logs
duration :: time_us() % microseconds between span start/end
}).
-type span() :: #span{}.
-type maybe_span() :: span() | undefined.
Passing the span structure between requests, this API will probably require to pass the span in function calls if the function has something to add to the span. This requires more code changes, however when functions pass non-strict composite structures (e.g. maps or proplists) then inserting the span information is more or less trivial.
Start span with name only. Name should refer e.g. to the interface.
-spec start(Name::info()) -> span().Start span with name and trace_id where trace_id e.g. received from protocol.
-spec start(Name::info(), TraceId::integer() | span()) -> span().Start span with name, trace_id and parent span id e.g. received from protocol.
-spec start(Name::info(), TraceId::integer(), ParentId::integer()) -> span().Start span with name and parent span. trace_id and parent span id are extracted from the parent.
-spec start(info(), ParentSpan :: span()) -> span().Add a tag to the previously started span.
-spec tag(Span::maybe_span(), Key::info(), Value::info()) -> maybe_span().Add a tag to the previously started span with additional service information.
-spec tag(Span::maybe_span(), Key::info(), Value::info(), Service::service()) -> maybe_span().Add a log/event to the previously started span
-spec log(Span::maybe_span(), Text::info()) -> maybe_span().Add a log/event to the previously started span with additional service information0
-spec log(Span::maybe_span(), Text::info(), Service::service()) -> maybe_span().End span and invoke the span filter (see below)
-spec finish(Span::maybe_span()) -> ok.Get span id's. Return the trace_id and the span id from the currently started span. This can be used e.g. when process "boundary" is to be passed and eventually new span needs this information. Also when these id's should be passed to a protocol interface for another system
-spec ids(maybe_span()) -> {trace_id(), span_id()} | undefined.example :
...
Span = otters:start("radius request"),
...
...
Span1 = otters:tag(Span, "request_id", RequestId),
...
...
Span2 = otters:log(Span1, "invoke user db"),
...
...
Span3 = otters:log(Span2, "user db result"),
Span4 = otters:tag(Span3, "user db result", "ok"),
...
...
Span5 = otters:tag(Span4, "final result", "error"),
Span6 = otters:tag(Span5, "final result reason", "unknown user"),
otters:end(Span6),
...The simplest API uses the process dictionary to store span information. This is probably the least work to implement in existing code.
Start span with name only. Name should refer e.g. to the interface.
-spec start(Name::info()) -> ok.Start span with name and trace_id where trace_id e.g. received from protocol.
-spec start(Name::info(), TraceId::trace_id() | span()) -> ok.Start span with name, trace_id and parent span id e.g. received from protocol.
-spec start(Name::info(), TraceId::trace_id(), ParnetId::span_id()) -> ok.Add a tag to the previously started span.
-spec tag(Key::info(), Value::info()) -> ok.Add a tag to the previously started span with additional service information
-spec tag(Key::info(), Value::info(), Service::service()) -> ok.Add a log/event to the previously started span
-spec log(Text::info()) -> ok.Add a log/event to the previously started span with additional service information
-spec log(Text::info(), Service::service()) -> ok.End span and invoke the span filter (see below)
-spec finish() -> ok.Get span id's. Return the trace_id and the span id from the currently started span. This can be used e.g. when process "boundary" is to be passed and eventually new span needs this information. Also when these id's should be passed to a protocol interface for another system
-spec ids() -> {trace_id(), span_id()} | undefined.Return the current span. e.g. it can be handed to another process to continue collecting span information using the functional API.
-spec span_get() -> maybe_span().
example :
...
ottersp:start("radius request"),
...
...
ottersp:tag("request_id", RequestId),
...
...
ottersp:log("invoke user db"),
...
...
ottersp:log("user db result"),
ottersp:tag("user_db_result", "ok"),
...
...
ottersp:tag("final_result", "error"),
ottersp:tag("final_result_reason", "unknown user"),
ottersp:end(),
...A note on the tag key/value and log types: the Zipkin interface requires string types. The Zipkin connector module (otter_conn_zipkin.erl) attempts to convert: integer, atom, and iolist types to binary. Unknown data types (e.g. record, tuples, or maps) are converted using the "~p" io:fwrite formating control character. The resulting string might be hard to read for non-Erlang people, but it is still better than loosing the information completely.
If the generation of log values is complex or computational expensive, a arity zero fun can be passed as info. The function is executed in the connector module and thereby after span_end has been called.
Adding service information to tags and logs means that otter adds a host structure to each of these elements. The extra optional service parameter in the relevant API calls can have 3 formats.
The atom default will include service/host information based on
the following configuration parameters of the zipkin connector.
...
{zipkin_tag_host_ip, {127,0,0,1}},
{zipkin_tag_host_port, 0},
{zipkin_tag_host_service, "otter_test"},
...Name of the service as a string in binary() or list() format also adds the host information based on the configuration above, except the service name will be as specified in the parameter.
A 3 element tuple {Service, Ip, Port} which will be used to compose
the information. This can be interesting to compose "ca" and "sa" opentracing
tags where the host information may refer to a remote server/client node
instead of the one where the span is generated.
There is no configuration involved in the stage of producing span data. The paramers mentioned above are functionally specific to the zipkin connector. It was simpler to explain them though in this context.
Please also consult the cuttle fisch schema file priv/otters.schema for valid configuration options.
The initial filter file can be configured with the filter_file app config value.
When the collection of span information is completed (i.e. finish is called), filtering is invoked. Filtering is based on the
tags collected in the span with the span name and the
span duration added to the key/value pair list with keys :
otter_span_name and otter_span_duration. The resulting
key/value pair list which is used as input of the filter rules. With the
examples above it can look like this :
[
{<<"otter_span_name">>, "radius request"},
{<<"otter_span_duration">>, 1202},
{<<"request_id">>, "6390266399200312"},
{<<"user_db_result">>, "ok"},
{<<"final_result">>, "error"},
{<<"final_result_reason">>, "unknown user"}
]This key/value pair list is passed to a sequence of conditions/actions pairs. In each pair the, conditions are a list of checks against the key/value pair list. If all conditions in the list are true, the actions are executed. An empty condition list always returns a positive match.
Otters uses a filter language that is dynamically compiled to a erlang module for performance. The Module is called ol_filter.
The filter language is loosely based on Erlang syntax and functions a bit like firewall rules.
A multiple filter rules can be used, and each filter can have multiple conditions on which actions are taken.
The general syntax is:
<name>([<condition>]) ->
<action>.Basic conditions are:
- none : (as in
()) always matches. <key> <comparison> <value>: wherecomparisonis either>,<,>=,=<,==or/=<key>: weather or not a key is present
Possible actions are:
drop: stops filtering for this and the following rules.skip: skips the rest of this rule and continues with the next.send: sends the spancontinue: only continues the current otherwise skipscount(<values>, ...): where values can either be a string'bla'which is taken literally or a keywordotter_span_durationto lookup the value.
Comparing the old style filters
[
{
%% Condition
[
{greater, "otter_span_duration", 5000000},
{value, "otter_span_name", "radius request"}
],
%% Action
[
{snap_count, [long_radius_request], []},
send_to_zipkin
]
},
{
%% Condition counts all requests with name and result
[
],
%% Action
[
{snap_count, [request], ["otter_span_name", "final_result"]}
]
}
]Translate to
slow_spans(otter_span_duration > 5000000) -> continue.
%% Skip requests that are not radius requests
slow_spans(otter_span_name == 'radius request') -> continue.
%% Count
slow_spans() -> count('long_radius_request').
%% Send
slow_spans() -> send.
%% Count them all
count() -> count('request', otter_span_name, final_result). {present, Key} {same, Key1, Key2}The value of a Key/Value pair can be compared to a value
{value, Key, ValueToCompare}example: check the name of the span
{value, otter_span_name, "radius request"}Key/Value pairs with integer values can be checked with the following conditions.
{greater, Key, Integer}
{less, Key, Integer}
{between, Key, Integer1, Integer2}example: check whether the span duration is greater than 5 seconds
{greater, "otter_span_duration", 5000000} {negate, Condition}example: Check if the final result is other than ok
{negate, {value, "final_result", "ok"}}Snapshot/Count increases a counter with a key composed by a fixed prefix and values of Key/Values in the Key/Value list. The key is a list of parameters. Also it stores the last span that triggers the counter in an ets table. These cheap snapshots can be used for initial analysis of eventual problems. The snapshots and counter can be retrieved by the otter counter API (see below).
{snapshot_count, Prefix, KeyList}example: snapshot/count any request that take long in different counters for each span name and final result. The condition example above with the otter_span_duration could be used to trigger this action.
{snapshot_count, [long_request], [otter_span_name, "final_result"]}This will produce a counter and snapshot with e.g. such key :
[long_request, "radius request", "ok"]This action triggers sending the span to Zipkin
send_to_zipkinNormally each span triggers checking of all Condition/Action pairs in the sequence (executing all relevant actions). However if for a particular set of conditions it is not necessary, the break action can be used. When this is found in an Action list then all actions in the current list are executed and no further Condition/Action pairs are checked.
breakThe filter rules are configured under filter_rules
example Condition/Action (rule) list:
[
{
%% Condition
[
{greater, "otter_span_duration", 5000000},
{value, "otter_span_name", "radius request"}
],
%% Action
[
{snap_count, [long_radius_request], []},
send_to_zipkin
]
},
{
%% Condition counts all requests with name and result
[
],
%% Action
[
{snap_count, [request], ["otter_span_name", "final_result"]}
]
}
]As a result of filter action send_to_zipkin the span is forwarded to the trace collector using HTTP/Thrift binary protocol. In the context of the span producing process the span is added to a buffer (ETS table). The content of this buffer is sent to Zipkin asynchronously in intervals configured in zipkin_batch_interval_ms (milliseconds).
The URI of the Zipkin trace collector is configured in zipkin_collector_uri.
Zipkin requires a node entry for every single tag collected in the span.
This entry contains the service name and IP/Port of the node sending the
span. If there is no tag/log is produced during span collecion with service/host
paramer, the Zipkin connector module (otter_conn_zipkin.erl) can be configured
to add an extra tag to each span during encoding the span by setting the
zipkin_add_host_tag_to_span in the configuration. The value of the
parameter should a tuple {Key, Value} which will be used as the
default tag information. OpenZipkin uses the "lc" (Local Component) tag
to display the service for a span.
example :
{zipkin_add_host_tag_to_span, {"lc", ""}},The default service/host information to be sent to zipkin is provided in zipkin_tag_host_service, zipkin_tag_host_ip and zipkin_tag_host_port configuration parameters.
It is also possible to add the default service/host information (as specified)
in the configuration paramers above to each tag/log that does not have it
explicitly set by setting the zipkin_add_default_service_to_logs and
zipkin_add_default_service_to_tags to true. This however can increase
the amount of data to be sent to zipkin significantly (depending on the
number of logs/tags) so probably it is not recommended for most uses.
example :
...
{zipkin_add_default_service_to_logs, false},
{zipkin_add_default_service_to_tags, false},
...Sending the span to Zipkin utilizes the ibrowse http client (which is the only dependency of OTTER).
As a result of the filter snap_count action, 2 ETS tables are used to count events (see snap_count action above) and in the same time store the last span information that has increased the counter. This can be considered a useful and fairly cheap troubleshooting tool.
Tho retrieve and manage these snapshot counters, OTTER provides API calls in the otter API module.
-spec counter_list() -> [{list(), integer()}].example:
3> otter:counter_list().
[{[long_span,test_request],1},
{[otter_conn_zipkin,send_spans,failed],1},
{[span_processed,"customer db lookup"],1},
{[span_processed,test_request],1},
{[long_span,"customer db lookup"],1}] -spec counter_snapshot(list()) -> term().example:
4> otter:counter_snapshot([long_span,test_request]).
[{[long_span,test_request],
[{snap_timestamp,{2017,2,21,19,8,23,76525}},
{data,{span,1487700503067982,3826404163842487863,
test_request,1113017739039451686,undefined,
[{customer_id,1},
{transaction_id,3232323},
{magic_tag,"wizz"},
{magic_result,error},
{db_result,"bad customer"},
{final_result,error}],
[{1487700503067998,"starting some magic"},
{1487700503068000,"finished magic"},
{1487700503068012,"db lookup"},
{1487700503076491,"db lookup returned"}],
8525}}]}] -spec counter_delete(list()) -> ok. -spec counter_delete_all() -> ok.The OTTER application configuration is handled through the otter_config module (otter_config.erl). In the default implementation it uses the application environment. An example configuration can be found in the otter.app.src file.
...
{http_client, ibrowse}, %% ibrowse | httpc
{zipkin_collector_uri, "http://172.17.0.2:9411/api/v1/spans"},
{zipkin_batch_interval_ms, 100},
{zipkin_tag_host_ip, {127,0,0,1}},
{zipkin_tag_host_port, 0},
{zipkin_tag_host_service, "otter_test"},
{zipkin_add_host_tag_to_span, {"lc", ""}},
{zipkin_add_default_service_to_logs, false},
{zipkin_add_default_service_to_tags, false},
{filter_rules, [
{
[
{greater, otter_span_duration, 1000}
],
[
{snapshot_count, [long_span], [otter_span_name]}
]
},
{
[],
[
{snapshot_count, [span_processed], [otter_span_name]},
send_to_zipkin
]
}
]},
...The development of ''otter'' was championed by Holger Winkelmann of Travelping. Both Travelping and bet365 kindly provided sponsorship for the initial development. The development was primarily done by Ferenc Holzhauser with design input from Chandru Mullaparthi.
Apache 2.0