+dev@xxxxxxx On Sun, Mar 8, 2020 at 5:16 PM Abhinav Singh <singhabhinav9051571833@xxxxxxxxx> wrote: > > I am trying to implement jaeger tracing in RGW, I need some advice > regarding on which functions should I actually tracing to get a good actual > performance status of clusters > > Till now I am able to deduce followings : > 1.I think we need to provide tracing functions where the `rgw` is > communicating with the librados, (particularly the librgw where the > communication is actually happening), because http request and response not > to be considered for tracing because that depends on clients internet speed. > 2.In librgw the functions like this here > <https://github.com/ceph/ceph/blob/0360bea127397a41eb282a1eef9af4ff4477b9d4/src/rgw/services/svc_rados.h#L166> > and > its corresponding overloading methods and also the this function here > <https://github.com/ceph/ceph/blob/0360bea127397a41eb282a1eef9af4ff4477b9d4/src/rgw/services/svc_rados.h#L169> > and > its corresponding overloaded functions. > 3.I see that pools are ultimately used to enter the crush algorithm for > writing data, so I think the ceation of pools should also be taken into > account while tracing,(creation of pool should be main span and these > functions > <https://github.com/ceph/ceph/blob/0360bea127397a41eb282a1eef9af4ff4477b9d4/src/rgw/services/svc_rados.h#L166> > should > be its child span). > > > Functionality of buckets like that of this > <https://github.com/ceph/ceph/blob/0360bea127397a41eb282a1eef9af4ff4477b9d4/src/rgw/services/svc_bi_rados.h#L44> > do not require tracing beacuse they are http requests. > > Any kind of guidance will be of great help. > > Thank You. > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > -- Cheers, Brad _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |