used to determine when a response is successful or not.
this controls what granularity is used for measuring latency. The default is milliseconds, but other values are valid. The choice of this changes the name of the stat attached to the given StatsReceiver. For the common units, it will be "request_latency_ms".
Convert the TypeAgnostic filter to a Filter and chain it with
andThen
.
Convert the TypeAgnostic filter to a Filter and chain it with
andThen
.
Terminates a filter chain in a ServiceFactory.
Terminates a filter chain in a ServiceFactory. For example,
myFilter.andThen(myServiceFactory)
a service factory that takes the output request type and the input response type.
Terminates a filter chain in a Service.
Chains a series of filters together:
Chains a series of filters together:
myModularService = handleExceptions.andThen(thrift2Pojo.andThen(parseString))
another filter to follow after this one
synchronously thrown exceptions in the underlying service are automatically lifted into Future.exception.
Conditionally propagates requests down the filter chain.
Conditionally propagates requests down the filter chain. This may useful if you are statically wiring together filter chains based on a configuration file, for instance.
a tuple of boolean and filter.
This is the method to override/implement to create your own Filter.
This is the method to override/implement to create your own Filter.
the input request type
a service that takes the output request type and the input response type
A
StatsFilter
reports request statistics including number of requests, number successful and request latency to the given StatsReceiver.The innocent bystander may find the semantics with respect to backup requests a bit puzzling; they are entangled in legacy. "requests" counts the total number of requests: subtracting "success" from this produces the failure count. However, this doesn't allow for "shadow" requests to be accounted for in "requests". This is why we don't modify metrics for backup request failures.