Gregory hi,
I'm sorry, I still don't see how next time an event like on the 8th of
November happens (which, correct me if i'm wrong, was a system wide issue),
I will have any tools to confront it. Your suggestion to pay the $500 fee,
seems to be the only solution (also suggested here by Google's B
I would suggest that Google splits the current availability percentage in
the system status into two values.
One related to applications using MS, the other related to applications
using HR. A single value for the hole system somehow doesn't make sense, as
this number won't be accurate to anyon
t: Re: [google-appengine] Re: Google App Engine's Team Dishonesty
Hi Greg,
can you please provide more information on you recent statement:
"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 S
Hi Greg,
can you please provide more information on you recent statement:
"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."
Does that mean that premier accounts get better uptime?
Thank you,
Andri
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
Excellent! Can I now plllease 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
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" 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
ime" may have been misconfiguration.
>
> > > Also even if you are correct that 99.5 isn't being met since they are
> > > at
> > > 98.2 or something along those lines, it is early in the yearly average.
>
> > > I'm all for calling people out
ot;
>
> Would an in dashboard SLA counter be awesome? Yes. But you are delusional
> if you think Amazon has ever been forth coming about issues.
>
>
>
>
>
>
>
> -----Original Message-
> From: google-appengine@googlegroups.com
>
> [mailto:google
pengine@googlegroups.com] On Behalf Of trilok
Sent: Sunday, November 20, 2011 1:07 AM
To: Google App Engine
Subject: [google-appengine] Re: Google App Engine's Team Dishonesty
Although I repeatedly asked you not to take this conversation to "Who's
fault is the downtime", you still d
g about issues.
-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of trilok
Sent: Sunday, November 20, 2011 1:07 AM
To: Google App Engine
Subject: [google-appengine] Re: Google App Engine's Team Dishonesty
Although I repeate
f
> 99.5.
>
>
>
>
>
>
>
> -Original Message-
> From: google-appengine@googlegroups.com
>
> [mailto:google-appengine@googlegroups.com] On Behalf Of trilok
> Sent: Sunday, November 20, 2011 12:03 AM
> To: Google App Engine
> Subject: [google-appeng
-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of trilok
Sent: Sunday, November 20, 2011 12:03 AM
To: Google App Engine
Subject: [google-appengine] Re: Google App Engine's Team Dishonesty
Mr Wirtz,
You have not read my
Mr Wirtz,
You have not read my response.
All of the examples I have given are Google issues since they are
presented in the system status.
I do know when my system is down for my fault and when it is down on
Google's fault. If you dive into the system status you will see that
even by their accou
You sited outage numbers greater than what Greg did. If your app was down
for your own fault then it is NOT a google issue.
If less than 1% experienced an outage of less than 5 minutes, and those apps
were idle then the number of "lost" pages was likely even lower.
You said they were not meeting
> -Original Message-
> From: google-appengine@googlegroups.com
>
> [mailto:google-appengine@googlegroups.com] On Behalf Of trilok
> Sent: Saturday, November 19, 2011 4:20 PM
> To: Google App Engine
> Subject: [google-appengine] Re: Google App Engine's Team Dishonesty
>
&
@googlegroups.com] On Behalf Of trilok
Sent: Saturday, November 19, 2011 4:20 PM
To: Google App Engine
Subject: [google-appengine] Re: Google App Engine's Team Dishonesty
OK, ok, ok, so we don't talk in theory (and to answer one question - the
errors are of requests that don't reach our app. T
Original Message-
> From: google-appengine@googlegroups.com
>
> [mailto:google-appengine@googlegroups.com] On Behalf Of trilok
> Sent: Saturday, November 19, 2011 3:42 PM
> To: Google App Engine
> Subject: [google-appengine] Re: Google App Engine's Team Dishonesty
>
42 PM
To: Google App Engine
Subject: [google-appengine] Re: Google App Engine's Team Dishonesty
Hello,
Me again :)
Yes, we are using HRD. Indeed since we moved to it (at least 4-5 months
ago), things became stabler... stable enough? Good question.
I have a monitoring SW (running on EC2) making
If I were "King of GAE", I would want to be very, very communicative about
issues that affect even only a portion of apps and users, e.g. having a
detailed hosting environment performance log (even if there is no in-depth
post-mortem, even just a one-line log item like: "There was a small service
d
Hello,
Me again :)
Yes, we are using HRD. Indeed since we moved to it (at least 4-5
months ago), things became stabler... stable enough? Good question.
I have a monitoring SW (running on EC2) making a request every minute.
In the past week this monitoring system gave me at least 2 errors per
day
FWIW, I've met a lot of the GAE team at various local events
(the privilege of living in the SF bay area) and I don't think any of them
would do something genuinely "dishonest". By and large they seem like
normal developers like you and I.
"Never attribute to malice what is adequately explained b
Thank you Gregory,
You say it affected a small portion of users and you later remove issue
notification from GAE status page which makes your status history and
availability counter look better as well for the new customers comming to
GAE and checking status page. Is this honest?
you never know,
Hello all,
Trying to show an accurate and honest representation of the status of a
massive distributed service is a really hard technical challenge but an
even harder conceptual one. While your app might be showing higher latency
or errors that doesn't indicate a systematic issue with the whole s
I have always wondered the same thing. One minute there is an issue, a
few days later it never happened.
Google is far from alone with such issues which is why there are
websites/services that monitor cloud status.
It may be a little unfair calling the app engine team dishonest.
Trying to change s
On 17 Nov., 15:24, trilok wrote:
> Google app engine hello,
> And now for the "cherry on the top", and the reason I used the word
> 'dishonesty' - You remove any note of the disruption from System
> Status.
I also find the Status Page extremely frustrating. The common
deployment issues are now sh
*+1*
*
*
*Can somebody from Google find the respect and comment here?*
*
*
On 18 November 2011 20:00, Olivier wrote:
> +1 for a more honest and consistent system status
>
> as for the issues, since we migrate to HRD, everything has run quite
> smoothly for us which is nice.
> Before that, it was
+1 for a more honest and consistent system status
as for the issues, since we migrate to HRD, everything has run quite
smoothly for us which is nice.
Before that, it was really, really bad on MS.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" gr
This input about System status is True. I have seen the system status
indicating problems in some days and some days later just "erase" that
the problem ocurred.
On 18 nov, 16:25, Robert Kluin wrote:
> I've seen at least two or three *major* disruptions on high-replication
> apps since GAE went
29 matches
Mail list logo
