> We would also like to be able to run A/B experiments.
I would like to see this in the form of percent experiments controlled by
prefs, which are pseudo-randomly set on update. This would mean that telemetry
would need to include dumps of relevant prefs. It would also make it easier to
set def
Robert Kaiser wrote:
Taras Glek schrieb:
I doubt people actually want to build own dashboards. I suspect this is
mainly a need because of deficiencies in the current dashboard.
I disagree. I think people will want to integrate Telemetry data in
dashboards that connect data from different sou
Taras Glek schrieb:
I doubt people actually want to build own dashboards. I suspect this is
mainly a need because of deficiencies in the current dashboard.
I disagree. I think people will want to integrate Telemetry data in
dashboards that connect data from different sources, and not just
Tel
Benjamin Smedberg schrieb:
Because the raw crash files do not include new metadata fields, this has
led to weird engineering practices like shoving interesting metadata
into the freeform app notes field, and then parsing that data back out
later. I'm worried about perpetuating this kind of behavi
On Thursday, February 28, 2013 9:57:04 AM UTC-8, Taras Glek wrote:
> Justin Lebar wrote:
>
> > It sounds to me like people want both
>
> >
>
> > 1) Easier access to aggregated data so they can build their own
>
> > dashboards roughly comparable in features to the current dashboards.
>
>
>
>
On Wednesday, February 27, 2013 12:52:10 PM UTC-5, Josh Aas wrote:
> I've been thinking about how we might improve access to telemetry data. I
> don't want to get too much into the issues with the current front-end, so
> suffice it to say that it isn't meeting my group's needs.
>
>
A few peopl
- Original Message -
> From: "Justin Lebar"
> To: "Benjamin Smedberg"
> Cc: "Benoit Jacob" , "Josh Aas"
> , dev-platform@lists.mozilla.org
> Sent: Thursday, February 28, 2013 9:14:52 AM
> Subject: Re: improving access to teleme
Justin Lebar wrote:
It sounds to me like people want both
1) Easier access to aggregated data so they can build their own
dashboards roughly comparable in features to the current dashboards.
I doubt people actually want to build own dashboards. I suspect this is
mainly a need because of def
On Thursday, February 28, 2013 12:14:52 PM UTC-5, Justin Lebar wrote:
> That is, I don't think we can or should export JSON with all the data
> in our databases. That is a lot of data.
We currently have a little over 20 TB of compressed telemetry documents stored
in HBase. The compression is LZ
It sounds to me like people want both
1) Easier access to aggregated data so they can build their own
dashboards roughly comparable in features to the current dashboards.
2) Easier access to raw databases so that people can build up more
complex analyses, either by exporting the raw data from the
On 2/28/2013 10:59 AM, Benoit Jacob wrote:
Because the raw crash files do not include new metadata fields, this has
led to weird engineering practices like shoving interesting metadata into
the freeform app notes field, and then parsing that data back out later.
I'm worried about perpetuating thi
On 2013-02-28, at 10:44 AM, Benjamin Smedberg wrote:
> On 2/28/2013 10:33 AM, Benoit Jacob wrote:
>> Please, please make your plans include the ability to get raw text files
>> (CSV or JSON or something else, I don't care as long as I can easily parse
>> it).
> Could you be more specific? Note th
On Thu, Feb 28, 2013 at 10:36 AM, Benjamin Smedberg
wrote:
> Cool. Perhaps we should start out with collecting stories/examples:
>
In that spirit:
What I almost always want to do is simply "for the last N days of
variable X show me a CDF (at even just 10 percentile granularity) for
the histogra
2013/2/28 Benjamin Smedberg
> On 2/28/2013 10:33 AM, Benoit Jacob wrote:
>
>> Please, please make your plans include the ability to get raw text files
>> (CSV or JSON or something else, I don't care as long as I can easily parse
>> it).
>>
> Could you be more specific? Note that while the text fi
On 2/28/2013 10:33 AM, Benoit Jacob wrote:
Please, please make your plans include the ability to get raw text files
(CSV or JSON or something else, I don't care as long as I can easily parse
it).
Could you be more specific? Note that while the text files currently
provided on crash-analysis, the
On 2/28/2013 10:18 AM, Josh Aas wrote:
On Thursday, February 28, 2013 8:16:50 AM UTC-6, Benjamin Smedberg wrote:
Have we discussed this project with the metrics team yet?
When I started looking into this it wasn't clear to me that people really knew
what they wanted
Cool. Perhaps we should s
Please, please make your plans include the ability to get raw text files
(CSV or JSON or something else, I don't care as long as I can easily parse
it). I don't have use for the current frond-end, and I believe that no
front-end will cover everyone's needs, and not every developer is familiar
with
On Thursday, February 28, 2013 8:16:50 AM UTC-6, Benjamin Smedberg wrote:
> Have we discussed this project with the metrics team yet?
When I started looking into this it wasn't clear to me that people really knew
what they wanted - they just knew why the existing system didn't work for them.
My
On 2/27/2013 12:52 PM, Josh Aas wrote:
The top priority for exposing telemetry data is an easy-to-use API.
Secondarily, there should be a default front-end.
I have used the telemetry data for only very specific purposes, and in
those cases it turns out that the existing frontend was absolutely
19 matches
Mail list logo
