[
https://issues.apache.org/jira/browse/THRIFT-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733394#comment-16733394
]
Randy Abernethy commented on THRIFT-2927:
-----------------------------------------
There are a lot of external solutions for observability. For example, the
service mesh model often used in cloud native systems provides
monitoring/metering access points at each service ingress/egress (e.g.
[https://istio.io/).] There are also cross platform tracing solutions that
offer some of these features (e.g. [https://opentracing.io/,]
[https://www.jaegertracing.io/).] To Jens' point leaving these concerns as a
choice external to thrift makes it optional and allows people to make choices
that will work for all of their platform elements (Thrift, messaging, REST,
custom, etc.).
> Statistic function support (call analytics: duration, success-count,
> failure-count, etc..)
> ------------------------------------------------------------------------------------------
>
> Key: THRIFT-2927
> URL: https://issues.apache.org/jira/browse/THRIFT-2927
> Project: Thrift
> Issue Type: New Feature
> Components: C++ - Compiler, C++ - Library
> Affects Versions: 0.9.2
> Environment: linux c++
> Reporter: Shi Jun
> Priority: Major
>
> As a RPC framework, Thrift should support some statistic function, such as
> latency、call times、failure rate and so on. And all these things can be done
> by the framework, applications just need to use a make argument to open the
> statistic function switch or not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
