looks like it was briefly fixed but nothing is reported for 6-30
Still down. No word on ETA.
Also, I’d like to take this time to complain about the severely lacking data points in Analytics (even when they ARE populating). Why did we get a big step BACKWARDS? We used to have unique users, time, etc.
Is this a signal from Corona that Analytics are going away like Corona Cloud and we should be using Flurry instead?
I was thinking the same thing. which is fine - the SDK is far more important - just would be good to know one way or the other
Might as well. Can analytics, support full Flurry SDK and put the extra resource back in the Corona SDK bug fix queue. Sounds like a plan to me!
Interesting points you guys make re: Flurry. Just tell us so we stop spinning our wheels looking at Corona’s analytics page and we’ll just bite the bullet and switch to Flurry.
If I remember right it seems like CC was tied to Analytics. I wonder if this recent outage is related to CC being taken down?
Paging Corona team.
I’ve been working on fixing analytics for past couple of days. Right now I don’t have a solid ETA for resumption of service but rest assured we’re not ignoring the issue. When you’re dealing with 5 billion row tables things take longer than one might like.
Perry,
I understand that the volume of data presents a lot of complex issues, but I don’t feel that’s an acceptable excuse for another period of downtime, given that all data prior to March 20 was wiped and we already went through one big period of downtime.
Anyhow - we’ll all deal with it, and the value you all provide with the SDK is 100x more important than the analytics, but it is frustrating on our end.
Still down. No word on ETA.
Also, I’d like to take this time to complain about the severely lacking data points in Analytics (even when they ARE populating). Why did we get a big step BACKWARDS? We used to have unique users, time, etc.
Is this a signal from Corona that Analytics are going away like Corona Cloud and we should be using Flurry instead?
I was thinking the same thing. which is fine - the SDK is far more important - just would be good to know one way or the other
Might as well. Can analytics, support full Flurry SDK and put the extra resource back in the Corona SDK bug fix queue. Sounds like a plan to me!
Interesting points you guys make re: Flurry. Just tell us so we stop spinning our wheels looking at Corona’s analytics page and we’ll just bite the bullet and switch to Flurry.
If I remember right it seems like CC was tied to Analytics. I wonder if this recent outage is related to CC being taken down?
Paging Corona team.
I’ve been working on fixing analytics for past couple of days. Right now I don’t have a solid ETA for resumption of service but rest assured we’re not ignoring the issue. When you’re dealing with 5 billion row tables things take longer than one might like.
Perry,
I understand that the volume of data presents a lot of complex issues, but I don’t feel that’s an acceptable excuse for another period of downtime, given that all data prior to March 20 was wiped and we already went through one big period of downtime.
Anyhow - we’ll all deal with it, and the value you all provide with the SDK is 100x more important than the analytics, but it is frustrating on our end.