On Nov 17, 2014, at 9:13 AM, Nuria Ruiz nu...@wikimedia.org wrote:
Since event logging in beta and production appear to be separate, I was
wondering if it would be possible to set up separate dashboards for beta and
production.
Dashboards can only be created o production data, Joel. We
Dashboards can only be created o production data,
From product we are constantly encouraged to be data-driven (measure
twice, implement once). When I read that we need to be in production to
get metrics, it feels like a circular dependency: Product wants us to have
numbers that justify the
+2
If the beta environment isn’t supposed to be used for beta testing, it
shouldn’t be called beta.
I’m all for grabbing the data and doing our own visualizations, but there is no
guarantee that any data we grab will be accurate since they data in the beta db
may be blown up at any time.
Nuria Ruiz, 17/11/2014 19:53:
I think there is a confusion between the not so well named beta
environment (testing environment in labs, which is what our thread
refers to) and being a beta-feature.
AKA https://bugzilla.wikimedia.org/show_bug.cgi?id=56537
Nemo
Joel,
Please look at the wiki page for beta features: The primary purpose of
Beta Features is to allow for Wikimedia designers and engineers (from the
Wikimedia Foundation and community alike) to roll out technical
improvements in an environment where large numbers of users can test, give
This is normally what product refers to as beta. You can, of course,
confirm.
I think that the Product team is already aware that Content Translation is
not a beta feature. It is deployed on beta-labs, but it is used by users
to create articles that later they copy and publish to a real
I find the idea that beta is an stable environment where users can try
stuff is not in sync with the fact thatbeta-labs is a release and QA
testing environment for every single team.
For example: we are actually about to test some changes to EL on our end,
those will affect data gathering on our
Nuria wrote:
I find the idea that beta is an stable environment where users can try
stuff is not in sync with the fact thatbeta-labs is a release and QA testing
environment for every single team.
Agreed. Whatever we would like “beta” to be it is clearly not a stable
environment and
[+ Ori]
Joel, Ori looked into this now. There was a problem with EL in labs which
affected logging events from Beta. Ori has fixed the issue, and the fix is
waiting approval from ops. Let's touch-base tomorrow to see if we see events.
Leila
This is great news! Thank you so much for
Joel, Ori looked into this now. There was a problem with EL in labs which
affected logging events from Beta. Ori has fixed the issue, and the fix is
waiting approval from ops. Let's touch-base tomorrow to see if we see
events.
In order to be able to properly test whether the fix fixes this issue
Please let me know if there is any way I can help out or if there is
anything you need from our end.
When you have deployed your newest code to production, let's check whether
events appear on the production stream. Let us know when deployment is done
and you think your code should be logging.
To
Hi Nuria,
Please let me know if there is any way I can help out or if there is
anything you need from our end.
When you have deployed your newest code to production, let's check whether
events appear on the production stream. Let us know when deployment is done
and you think your code
Joel:
I see, I was hoping to set aside the beta issues but if you are not
deploying to prod any time soon I guess we will need to troubleshoot there.
By the looks of it EL has not worked in beta since august, but, as I said
before, I know very little about how beta is put together.
I have filed
[+ Ori]
Joel, Ori looked into this now. There was a problem with EL in labs which
affected logging events from Beta. Ori has fixed the issue, and the fix is
waiting approval from ops. Let's touch-base tomorrow to see if we see
events.
Leila
On Thu, Nov 13, 2014 at 1:30 PM, Nuria Ruiz
14 matches
Mail list logo
