I am working on gwt application with google app engine as a server. I have put the logs and appstat filter, so that i could know that what is the latency time.
Suppose if i open a link it is showing that 118ms for appstats (real=118ms) and 90ms for coming back through my login filter, so it is totally 208ms but in the firebug net panel it is showing 705ms for onload for the first request,
Any body have any idea, please let me know.
Thanks
MSNaidu
It would be a really difficult to figure our whether firebug is recording incorrectly or if there is genuine lag. You should try cross confirming by using Chrome SpeedTracer and Chrome's Dev Tools Network, Timeline and Audits features.
Related
I have website developed using nodejs and react server side rendering.
When i am trying to scrape my website with facebook debugger, facebook takes more than 10 sec and times out. However I noticed that my web server responds to facebook scraper request within few milliseconds.
Also, Page performance is fine and it serves in less than 2 secs at max.
Note: FB debugger can scrape my website homepage (which is static file) without any issues. Not sure what is causing facebook debugger to timeout.
Any ideas?
I had path which was blocking the request, fixing that but fixed the issue.
#souhailhimself thank you for pointing in the right direction.
the last week my php flex app on app-engine has been causing error 500, sometimes. I dont have changed nothing in my code. But the strangest is that nothing is shown in the error reporting panel. Someone knows if there are new updates or something like that for App Engine?.
Regards.
The last change on December 9, 2019 is about:
App Engine is changing the URLs that you use to send requests to your apps. You can now include a region ID to help Google route your requests more efficiently and reliably. For example, an app can receive requests at https://PROJECT_ID.REGION_ID.r.appspot.com. This new URL is optional for existing apps, and will soon be required for all new apps
https://cloud.google.com/appengine/docs/flexible/php/release-notes
Maybe this could be causing some internal erros. It would be nice more details bout the 500s errors.
Finally, I found the error logs of my app, they are in Stackdriver Logs Viewer. And not in the Error Reporting Panel
Blessings.
We were running on AppEngine but recently moved over to Managed VMs. For some reason AppStats is no longer available? We just get a 404 not found error when browsing to our appstats URL. Is appstats not supported on Managad VMs? If not, is there a way of isolating poorly performing endpoints within our application?
One way to isolate poorly performing endpoints is to use the advanced filter search in the GCP Logs Viewer. It is a little hard to find at first.
To get there, in your Google Cloud console, navigate to Logging for your project. At the right of the text box for "Filter by label or text search" you will see a small dropdown arrow. Click that and select "Convert to advanced filter". This will allow you to write your own sql-ish query where you can find requests that took longer than n to complete.
For example, add the following to the filter:
protoPayload.latency>"0.300s"
This will return a list of all requests that took longer than 300 milliseconds to process. If you have Cloud Trace enabled, you can click on the request response time to see the timeline for the individual service calls.
Good afternoon.
We've recently noticed a growing number a API call failure when trying to reach your Google Static Maps API.
Issues initially seemed intermittent, but seems to happen a lot more frequently, if not: all the time.
What steps will reproduce the problem? Please provide a link to a
demonstration page if at all possible, or attach code.
Totally works locally or in a web browser
Sends out a 500 Internal Server Error when on our staging/production systems
Could that be related to authentication? To my knowledge, API keys aren't really enforced locally, but definitely checked for when application runs on a live system.
Doesn't report as an error in our Google API Console. Just as a regular successful call.
Sample URL:
https://maps.googleapis.com/maps/api/staticmap?center=38.121504,-122.590525&scale=2&visual_refresh=true&size=280x188&key=OUR_BROWSER_API_KEY&markers=icon:http://stage.hometrendsreport.com/images/mini_orange.png|shadow:false|38.121504,-122.590525&markers=icon:http://stage.hometrendsreport.com/images/mini_blue.png|shadow:false|38.121073,-122.5932|38.123742,-122.591363|38.123981,-122.590448|38.124226,-122.589497|38.118754,-122.588585|38.119648,-122.587095|38.123877,-122.587494|38.118187,-122.592065|38.118038,-122.591357&markers=icon:http://stage.hometrendsreport.com/images/mini_gray.png|shadow:false|38.118442,-122.589865|38.118442,-122.589865|38.12166,-122.602269|38.116919,-122.571937
Here's our code snippet, using ruby/paperclip:
self.picture = URI.parse(google_map_url.to_s)
return self.save
Any idea why this is happening?
Any help gladly appreciated.
Best regards,
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
When I access the link I get an "invalid API key", so the API Key may be the problem. I believe there are also much lower quota for requests to the static map API, while testing you may have exceeded your quota.
I'm having an white screen of death when trying to debug my silverlight application. The problem is that I don't know what causes it and I don't get any type of information from either Visual Studio or the browser itself (IE9). Breakpoints won't be hit as App() in the App.xml.cs doesn't get fired either.
The application works fine on my own laptop, but I'm trying to make final adjustments to it on the server which will host the application once it's done. The problem occures on this server.
Would there be any way to get information about what's causing it or did someone experience simulair issues?
hit F12 in IE and go to network and start capturing. You should see your error there if something went wrong downloading and also if there was a problem with the Silverlight plugin (check Console or Script tag).
There could be a number of reasons for this including problems with database connectivity, WCF services, and many other factors. One thing that might help you get some information is a product called Fiddler. If you are able to download and install that on your development machine, you can have it running when you try and access your application on the server. It will give you messages for every step of your application initialization, including database authentication, service authentication, the xap file transfer, etc.
My problem was related to init params not loading up from the web project's .aspx page, try having a look at this if you are having "white death screen" issues.