Hi there, I've started to look at using the new CloudTrace API to add information on CloudSQL requests to traces on AppEngine requests, which we desperately need, but I encountered two challenges:
First, even batching all the traces for a request together in a single API call adds about 100 ms latency to the request (that's the /urlfetch.Fetch bar below), which I don't think I can stomach in production. Is there anyway to piggy back custom trace data onto AppEngine's existing reporting mechanism, which seems to run independently of requests? Second, is there any way to detect which requests AppEngine has sampled for tracing so that we only spend the time to report traces for those that are sampled for RPC traces? Thanks, Alex <https://lh3.googleusercontent.com/-NPC894TI-ws/Vqqf5Kna_WI/AAAAAAAABKI/hwK5scVl5mM/s1600/trace.png> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0968a1ca-db6d-440d-983f-dc5182097aa3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
