-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add profiling support for Thrift services #329
Comments
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
May 29, 2015
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
May 29, 2015
…onous processor operations
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
May 29, 2015
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
May 29, 2015
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
May 29, 2015
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
May 29, 2015
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
Jun 1, 2015
Xylus
added a commit
that referenced
this issue
Jun 1, 2015
#329 modify ITs to retrieve hostnames from InetSocketAddress
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
Jun 1, 2015
Xylus
added a commit
that referenced
this issue
Jun 1, 2015
#329 added hostname modification to Annotation checks
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
Jun 5, 2015
This was done to ease up future refactoring that would pull up trace headers used for tracing various RPC calls into a single common class.
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
Jun 19, 2015
…l timing issues * Span/SpanEvent order for client/server traces cannot be guaranteed with the current implementation of OrderedSpanRecorder. Client/server trace verification tests are therefore seperated. * Async call tests are disabled as well as the current implementation of OrderedSpanRecorder does not adequately support async client SpanEvents. A modification should be in place soon, and these tests will be added to the suite when that happens.
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
Jul 14, 2015
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
Jul 14, 2015
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
Jul 14, 2015
Thrift integration tests may fail occasionally when a new test starts and creates a socket on a port which wasn't properly released (or is still in the process) by the previous test. |
Xylus
added a commit
to Xylus/pinpoint
that referenced
this issue
Nov 9, 2018
Xylus
added a commit
that referenced
this issue
Nov 9, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thrift services may be traced by intercepting Thrift clients, and Thrift processors.
These interception points are:
org.apache.thrift.TServiceClient
org.apache.thrift.async.TAsyncClient
org.apache.thrift.TBaseProcessor
org.apache.thrift.TBaseAsyncProcessor
org.apache.thrift.transport.TSocket
org.apache.thrift.transport.TNonblockingSocket
org.apache.thrift.transport.TFramedTransport
org.apache.thrift.transport.TFastFramedTransport
org.apache.thrift.transport.TSaslClientTransport
org.apache.thrift.transport.TMemoryInputTransport
org.apache.thrift.protocol.TBinaryProtocol
org.apache.thrift.protocol.TCompactProtocol
org.apache.thrift.protocol.TJSONProtocol
org.apache.thrift.protocol.TTupleProtocol
may also be possibleThere are 4 main interception groups for tracing various Thrift operations.
Each of these operations work similarly by utilizing the interception points above:
Will test against Thrift v0.8.0+ except for asynchronous processors which have been added in 0.9.1.
The text was updated successfully, but these errors were encountered: