Hi,
If you are as far as to send your data to statsd (hopefully this is the
same statsd other teams are using), wouldn't the already functioning
graphana stack will suffice for your graphing needs?
Dashboard:
Thanks,
Nuria
On Fri, Jan 9, 2015 at 9:20 PM, E.C Okpo <ecokpo(a)gmail.com> wrote:
Hi,
In terms of where the data will be coming from, it will be coming from
node-txstatsD, a port of statsD/node-statsD, a statsD client. I had
previously been working on using Event Emitters in conjunction with statsD,
but node-txstatsD seems to solve the task of obtaining and sending timing
to a visualization front-end.
The data to be visualized will be timing (in ms), counts, and maybe
sizes(KB, MB).
Based on this, what would be the recommended front-end to then visualize
the information?
Message: 1
Date: Tue, 30 Dec 2014 07:37:35 -0800
From: Nuria Ruiz <nuria(a)wikimedia.org>
To: "A mailing list for the Analytics Team at WMF and everybody who
has an interest in Wikipedia and analytics."
<analytics(a)lists.wikimedia.org>
Subject: Re: [Analytics] Performance Visualization Frontend
Message-ID:
<
CAMpYYkG4aVNLFJL3p6+a2mH3gTcntH7oxu+haGFsdaA_ig2Qzw(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello,
The more important question is where will your data come from: event
logging? graphite? elsewhere? visualization comes secondary to this.
EventLogging is a good solution for structured, somewhat complex,
application data, graphite is s good solution for plain counters, which is
well suited to perf data. Let us know if you already have data and we can
proceed from there.
Thanks,
Nuria
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics