+1 for graphite and grafana via Verisign's plugin. Using graphite a few years ago was a real game changer for us, and more recently grafana to help build out dashboards instead of copy/pasting graphite urls around. Here's two different dashboards we have relating to our storm topologies. We're able to correlate information from all parts of our app, hardware monitoring metrics (via zabbix) and of course storm. Additionally we use seyren on top of graphite for our alerting as well.
bolt specific dashboard <http://i.imgur.com/ftKtci5.png> Dashboard correlating lots of related information from various sources <http://i.imgur.com/t7yJ8d5.jpg> On Mon, May 30, 2016 at 9:13 AM, Radhwane Chebaane <[email protected] > wrote: > Hi Matthew, > > We actually use the InfluxData <https://influxdata.com/> Stack (InfluxDb > + Grafana). > We send our data directly to a time-series database, *InfluxDB* > <https://influxdata.com/time-series-platform/influxdb/>. Then, we > visualize metrics with a customizable dashboard, *Grafana* > <http://grafana.org/>. > This way, you can have real-time metrics on your Storm topology. You may > also add custom metrics for enhanced monitoring. > > To export Storm metrics to InfluxDB you can use this *MetricsConsumer *which > is compatible with the latest version of InfluxDB and Storm 1.0.0: > https://github.com/mathieuboniface/storm-metrics-influxdb > > Or you can use the old Verisign plug-in with Graphite protocol: > https://github.com/verisign/storm-graphite > > Best regards, > Radhwane CHEBAANE > > > On 30/05/2016 14:47, Matthew Lowe wrote: > > Hello all. > > What kind of monitoring solutions do you use with storm? > > For example I have a bash script that reads the Json data from the REST UI > and alerts if there are any bolts with high capacities. > > It's only small and hacky, but I am genuinely interested to how you all > monitor your topologies. > > Best Regards > Matthew Lowe > > >
