thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "郑华斌" <huabin.zh...@qq.com>
Subject Best way to sniffer thrift requests
Date Tue, 11 Jul 2017 09:16:13 GMT
For service S, it has N apis, what's the best way to copy requests of specified apis and resend
them to a message queue, without affecting the normal service?


Maybe there are following possible ways:
1) tcp copy: with tcp copy tools that copy requests on the server side, and redirect the copied
flow to a fake server, there requests of different apis are send to message queue, in the
format of api:serialized_request. But deploying is difficult because tcpcopy requires root
permission.
2) develop a transport to wrapped current transport on server side, and send buffers to mq
as well as call underline transport. But how to identify which api a request buffer belong
to?


Any ideas?
Mime
  • Unnamed multipart/alternative (inline, 8-Bit, 0 bytes)
View raw message