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
worthless. I had to get metrics to implement a custom report (which
currently runs on a cronjob) for bug 789697.
I fully support the ability for people to query the telemetry data
directly. That said, do we know how this would actually work in
practice? elasticsearch apparently doesn't store all the data, and hbase
is usually a pain to query. I don't know of any existing frontend to
make queries not suck. So basically this sounds like a proposal that
somebody actually write a frontend.
I know that the Socorro team has already spent some significant time
writing an elasticsearch frontend which would let us perform complicated
queries on crash-stats, and as I understand it it's pretty generic so we
might be able to reuse that frontend for telemetry as well. Perhaps this
means that the telemetry elasticsearch instance should contain all of
the telemetry data, and not just specific fields? cc'ing Laura who can
help provide background/insight.
... It should not require people to apply for special privileges.
This may not be possible. Unless you simplify the query language so that
you can't do very expressive things with it, it's pretty easy to write
queries which are very cluster-intensive. I suspect that we will need to
do something to monitor query usage;we should be able to log who is
performing complex queries and inform them if they are affecting system
performance.
Have we discussed this project with the metrics team yet?
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
