IssueTracker

Currently the appstats gives you detail like this:

Request: GetRequest<key_=[Reference<app_='s~google.com:wizard', has_app_=1, has_path_=1, path_=Path<...>>], ...>
Response: GetResponse<entity_=[GetResponse_Entity<entity_=EntityProto<entity_group_=Path<element_=[Path_Element<...>]>, ...>, ...>]>
Stack:
  <path[7]>/google/appengine/datastore/datastore_rpc.py:1154 make_rpc_call()
  <path[7]>/google/appengine/datastore/datastore_rpc.py:1375 make_get_call()
  <path[7]>/google/appengine/datastore/datastore_rpc.py:1383 async_get()
  <path[7]>/google/appengine/api/datastore.py:626 GetAsync()
  <path[7]>/google/appengine/api/datastore.py:651 Get()
  <path[8]>djangoappengine/db/compiler.py:326 get_matching_pk()
  <path[8]>djangoappengine/db/compiler.py:100 fetch()
  <path[8]>djangotoolbox/db/basecompiler.py:234 results_iter()
  <path[8]>django/db/models/query.py:275 iterator()
  <path[8]>django/db/models/query.py:82 __len__()


It's great to be able to see how many RPC calls a page is doing, but this doesn't actually provide useful information about where they are occurring. There are two problems here:

1. The request is truncated, so all you see is useless protocol waffle. I'd really like to see the actual query params here! i.e. the kind and id(s) that were requested.

2. The stack trace also seems to be truncated? It doesn't show any frames from my actual application, it only goes down as far as the Django framework. If you must truncate it, why not chop the top off, instead of the bottom? i.e the first five lines are unnecessary (if I know it's a GetRequest) because I can't avoid using the google api.

This info would really help with performance tuning applications, reducing number of RPC calls etc.