Hi Vinny,
I'm running appstats but that request doesn't come through. Is there a way 
to make it appear with app stats? (other api calls do come through on app 
stats)


----------
To be clear, this is how I have appstats installed in appengine_config.py 
and app.yaml:

'''
start App Stats config
default link: /_ah/stats/
see https://developers.google.com/appengine/docs/python/tools/appstats
'''

appstats_CALC_RPC_COSTS = True

def webapp_add_wsgi_middleware(app):
    from google.appengine.ext.appstats import recording
    app = recording.appstats_wsgi_middleware(app)
    return app

'''End App Stats config'''


and 

builtins:
- appstats: on
----------------------

App stats works for most api calls e.g:
(1) 2014-05-20 20:08:05.073 "POST 
/_ah/spi/ArchiveDashEndpoint.getArchiveData" 200 
<http://robert-dot-td-admin.appspot.com/_ah/stats/details?time=1400645285073>real=15121ms
 
api=0ms overhead=72ms (43 RPCs, cost=133840, 
billed_ops=[DATASTORE_READ:1912])

however the request I asked about *doesn't come through in app stats *(which 
is why I asked if there is a way to investigate it): (ass you can see there 
are both robert-dot-modulename-appid and robert-dot-appid)



   1. Remote Address:
   xxxxx
   2. Request URL:
   
   
https://robert-dot-api-server-dot-xxxxx.appspot.com/_ah/api/discovery/v1/apis/xxxxx/v1/rpc?fields=methods%2F*%2Fid&pp=0
   3. Request Method:
   GET
   4. Status Code:
   304 Not Modified
   5. Request Headers
      1. :host:
      robert-dot-api-server-dot-xxxxx.appspot.com
      2. :method:
      GET
      3. :path:
      /_ah/api/discovery/v1/apis/xxxxx/v1/rpc?fields=methods%2F*%2Fid&pp=0
      4. :scheme:
      https
      5. :version:
      HTTP/1.1
      6. accept:
      */*
      7. accept-encoding:
      gzip,deflate,sdch
      8. accept-language:
      en-US,en;q=0.8
      9. if-none-match:
      "xxxxx/xxxxx"
      10. referer:
      
      
https://robert-dot-api-server-dot-xxxxx.appspot.com/_ah/api/static/proxy.html?jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.en.6SWenkOB4-I.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Fz%3Dzcms%2Frs%3DAItRSTPqnV0vyAsVqqzFCGu-iTJCnEAiGw
      11. user-agent:
      Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 
      (KHTML, like Gecko) Chrome/34.0.1847.137 Safari/537.36
      12. x-clientdetails:
      
      
appVersion=5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_9_2)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F34.0.1847.137%20Safari%2F537.36&platform=MacIntel&userAgent=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_9_2)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F34.0.1847.137%20Safari%2F537.36
      13. x-goog-encode-response-if-executable:
      base64
      14. x-javascript-user-agent:
      google-api-javascript-client/1.1.0-beta
      15. x-origin:
      https://robert-dot-xxxxx.appspot.com
      16. x-referer:
      https://robert-dot-xxxxx.appspot.com
      


btw - the appstats link i'm using 
is http://robert-dot-xxxxx.appspot.com/_ah/stats/? and appstats is only 
deployed to that version. I can't make that version the default for 
production but this api is only running on my version anyway.

On Friday, 16 May 2014 17:59:32 UTC+12, Vinny P wrote:
>
> On Thu, May 15, 2014 at 4:20 PM, Robert King 
> <kingrob...@gmail.com<javascript:>
> > wrote:
>
>> for 
>> example<http://stackoverflow.com/questions/23618638/google-cloud-endpoints-ah-api-discovery-v1-apis-myapi-v1-rpc-takes-half-a-minu>
>> , 
>> /_ah/api/discovery/v1/apis/archivedash/v1/rpc?fields=methods%2F*%2Fid&pp=0  
>> is often at times running slowly (e.g. waiting over 10 seconds on fast 
>> connection). I'd like to investigate it somehow.
>> Is it a problem elsewhere in my app (e.g. some of my webapp2 handlers 
>> have high latency due to doing many urlfetches etc) or is it a problem with 
>> endpoints that don't have much traffic?
>> I'm wondering if performance of /api/discovery can be effected if other 
>> parts of my app are experiencing high latency or is its performance self 
>> contained?
>>
>
>
>
> The best way to pinpoint performance issues is to record an AppStats run 
> of the request. Can you install AppStats (see instructions 
> here<https://developers.google.com/appengine/docs/java/tools/appstats>), 
> run an API request, then post the AppStats record back here?
>  
>
> -----------------
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> App Engine Code Samples: http://www.learntogoogleit.com
>  
>  

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Reply via email to