Hey guys, cc: harlowja, DinaBelova, boris-42
I saw a lot of great work in OSProfiler. I see that "Trace every N request configuration (not done yet)". [1] Both Zipkin [2] and OpenTracing [3] have this feature. OSProfiler aim to be a small library --> May this feature make any overhead? Do you guys have any idea how to implement this? [1] Mitaka spec: https://specs.openstack.org/openstack/oslo-specs/specs/mitaka/osprofiler-cross-service-project-profiling.html#performance-impact [2] Zipkin: http://zipkin.io/pages/instrumenting.html [3] OpenTracing: http://opentracing.io/documentation/pages/api/data-conventions.html Best regards, Vinh Nguyen Trong (tovin07/Tovin Seven) PODC - Fujitsu Vietnam Ltd. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
