Would it not make more sense for the team / teams that maintain statd &
graphite to maintain statv?
As far as I see statsv is part of that ecosystem and also as far as I know
the analytics team doesn't really have much to do with it.
On Mon, 14 Nov 2016 at 10:40 Gilles Dubuc
infodisiac.com/blog/201
> 4/03/wikimedia-editor-trends-broken-down-by-project/ .
>
> Nemo
>
>
> ___
> Analytics mailing list
> Analytics@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/analytics
>
--
Addshore
___
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
The query listed selecting from wikidatawiki.wb_terms was me /
wmde-analytics and runs daily.
I agree that some sort of query limits would make sense.
What limits are currently in place?
On Tue, 3 Jan 2017 at 21:04 Nuria Ruiz wrote:
> Sorry, that was me.
>
> >I would urge
As you spotted there are indeed some gaps (Dashiki & Report updater),
mainly due to the fact that WMDE don't use them currently.
I agree that if we want this as a general starting guide we should move the
WMDE specific stuff out / somewhere else.
On Mon, 20 Mar 2017 at 14:38 Dan Andreescu
r queries as received by
> the server. So you can "test" your queries agains a server and see how
> those are received.
>
>
> Thanks,
>
> Nuria
>
>
>
>
>
> On Sun, May 14, 2017 at 1:10 PM, Adrian Bielefeldt <
> adrian.bielefe...@mailbox.tu-dre
I just quickly tried this out live looking for a prefetch webrequest from
my chrome browser for a enwiki, enwiktionary and wikidata page but no
prefetching happened.
After a quick search I found
https://www.technipages.com/google-chrome-prefetch and confirmed that the
prefetch setting is ON in my