Hi Yoav,

I don't feel this thread hasn't been hijacked, but I'm not sure what your
question is at this point.  We typically do post an update when there is a
system-wide issue and we typically do a post-mortem as well.  So if you
question is "Can we post something when there are system-wide issues", the
answer is, yes, we typically do and we will continue to do so.

It seems that the question is around the definition of "system-wide issue",
while you might've seen 3 issues that does not mean they were widespread
problem.  The status dashboard is run from a small set of probers and so
there are times it will show issues on the status dashboard when it was a
very isolated problem or worse it was merely an issue with the prober.
 Should we fix this so that the status site is accurate?  As I said
previously, yes, we need a better way of doing this.  We have started
offering Premier Accounts (for $500/month) that provide operational support
so if you feel it is critical to your business to talk to someone when
there is an issue, you should sign up for a Premier Account.  The fee for
the premier account essentially pays for the people that you can contact
about issues (this is not a way for us to increase profits, its a way for
us to provide better service).

To be clear we are not going to post every single time there is any sort of
disruption to any application.  It isn't feasible to do so for a massive
multi-tenant distributed system running over 300,000 applications.  We will
continue to work on trying to find the appropriate level so that everyone
stays informed when there are issues.  But in the end there will be times
that you feel as if you have an issue, maybe slightly elevated latency, and
no one else is seeing a problem, this is what happens in large multi-tenant
distributed systems.  It sometimes is something you've done and sometimes
something going on with the serving infrastructure, if you want someone to
contact who will reply within a certain amount of time, get a Premier
Account.  That being said lots of App Engine team members monitor this list
constantly (well, when we're conscious) and you might sometimes get a reply.

The reason that the status site says the number that it does is because it
includes M/S and HRD apps so it is showing uptime for apps not under SLA.

Jeff is correct, whenever you assume we are insidiously trying to trick
you, its probably a better assumption that there is a bug, or a
misconfiguration or, even, very rarely, someone made a mistake, we are
human.  Frankly, anyone assuming that we are trying to lie in order to hide
issues says more about that person than it does about the App Engine team.

Brandon is also correct in that you don't need to accuse us (or in this
case, me) of flawed morals in order to get attention.  There are plenty of
people we talk to all the time simply because they have a question.  If you
accuse me of lying to you I will most likely take a more defensive stance
than I would otherwise and ask for your evidence, again, I'm human.

Lastly, I sent a similar response about 24 hours ago, I thought I had
answered your question at that point, so I'm not sure if this answers it or
not.

TL;DR want someone to talk to when you are having issues, pay for a premier
account.

Greg

On Sun, Nov 20, 2011 at 7:08 AM, Yoav Amit <[email protected]> wrote:

> Excellent! Can I now plllllllllllllllllllease get someone at Google to
> comment on the transparency issue?
>
> Is there any chance that next time GAE is at a very elevated status, as
> seldom as that may occur, we the paying users can get a description of the
> problem and a rough estimate of how long will it take to solve the problem
> during real-time? Just something so small to hang on to and pass to
> our frustratingly angry clients?
>
> I am literally on my knees begging. I'll upload a pic of me begging if I
> can get 10 +1's on this :)
>
>  - Yoav.
>
>
> On Sun, Nov 20, 2011 at 4:43 PM, WallyDD <[email protected]> wrote:
>
>> Could this be threatening behaviour? I'll let someone else decide.
>>
>> Both of you. Knock. It. Off.
>>
>>
>> On Nov 20, 4:52 am, "Brandon Wirtz" <[email protected]> wrote:
>> >
>> > Calling the team dishonest.  Where I grew up calling someone a liar is
>> the
>> > kind of thing that gets your nose bloodied.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>>
>
>
> --
>  - Yoav
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to