First of all, let me state that I love App Engine, I've been using App Engine since the very early days, and what hurts me the most if the state of dismay that I feel the product is in, and getting the feeling that those working on the product, not loving and caring the product, as the early engineers did
So, the issue, I originally reported at: https://groups.google.com/forum/#!topic/google-appengine/95VB910CdzI *TL;DR:* Errors on an internal network layer can happen, yet these issues are not logged in our Console's, they are logged in the network layer, we can't see them, Google can see them, yet, even when they could, they don't propagate these issues to our App Engine logs, even though I reported and requested it months ago, and, in my opinion, it's a critical issue and a *major breach of trust* Why the harsh language, and the accusation of `*being scammed*` - Well, there's no way to assess actual error rates, see the errors, maybe the error rates are 0.5%, way above SLA guarantees, but as App Engine using developers, there's no way for us to know, as errors are being hidden, rather than being reported - so in order to actually catch these errors, you need to implement your own logging for various different usage scenarios Technically, 2 problems: *1)* Request is made, it never hits App Engine, it never gets logged, client sees error, but as the developer, you never see it *2) *Request is made, it hits App Engine, the result never hits the requester, the requester sees 500, while the actual operation is a 200 Depending on your architecture, scenario (1) is better, if you are doing critical operations, (2) could require manual intervention I'm developing http://adventure.land - an mmorpg that uses App Engine for backend, while it's a game, to prevent item duplication and to ensure data singularity, the operations need to be precise, at this point, it's pretty much like a bank infrastructure, If you check our Discord: https://discord.gg/44yUVeU and search for "App Engine" - you can see how torturous this issue is - my entire architecture now assumes a backend that can fail at any time for long durations (which is kind of nice, but, scenario (2) is out of the scope of this system, it requires an entirely different approach, which I'm not sure how to approach, yet) Holiday season is a very critical time, I'm way behind schedule, I want to release my game, yet, once again, an App Engine issue ruined my time and wasted the day Please fix this issue, report the errors, and try to prevent scenario (2) as much as possible -- 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 https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/4aab5e66-a51f-46f6-b60f-d19565d9c17f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
