angularjs-graphite

Predefined services, factories, directives for Graphite

Module License: Apache License, v2.0

Added by: Sam Deering

GitHub

Repository

cmaurer/angularjs-graphite

Stats

Stars: 12

Watchers: 12

Forks: 2

Module Description

angularjs-graphite

Predefined services for Angular.js to make integrating with Graphite simple, quick, & effective

Build Status Coverage Status devDependency Status Bitdeli Badge

Design Thoughts

Server Configuration

  • Environment(s)
  • URL's, ports
  • Security, CORS, etc

Metric Search

  • Enable find all metrics

Datatype Facade

  • Always communicate with graphite via raw (should be most efficient) datatype, expose json, csv, or raw passthrough
  • enable formatting between datatypes

Time Facade

  • Expand time formatting beyond the api that graphite exposes
  • 'HH:mm_YYYYMMDD'

Render API Facade

Typical url format

url:port:target(s):from:until:format

Typically there is a lot of code that looks something like the following

"alias(sumSeries(exclude(asPercent(nonNegativeDerivative(server1.procfs.stat.cpu.)),'idle')),'server1')," + "alias(sumSeries(exclude(asPercent(nonNegativeDerivative(server2.procfs.stat.cpu.)),'idle')),'server2')," + "alias(sumSeries(exclude(asPercent(nonNegativeDerivative(server3.procfs.stat.cpu.)),'idle')),'server3')," + "alias(sumSeries(exclude(asPercent(nonNegativeDerivative(server4.procfs.stat.cpu.)),'idle')),'server4')," + ...

Repetitively creating target urls, where the only thing that typically changes is the specific server name. That can be different based on the specific graphite server instance.

How can it be abstracted out to something less repetitive?

API URL Builder Given a set of servers, formulas, build the corresponding url's

Incremental Query

  • Ability to cache results and only query a smaller amount of time
  • For example for a multi-time period query, cache the results from the first request on subsequent requests, only query for the last n-period(s) of time combine the results back into one complete result

The goal is to reduce the number of calls to graphite.

Aggregation, Parallelization, Routing

  • Route requests to specific servers for improved performance
  • Parallelize requests
  • Aggregate responses into combined format

Caching

Promises, Promises yeah, Im a child of the 80's

Enable composition of Metric Urls easier

  • writing dashboards, apps can get really hairy with a lot of urls.
  • Is there an angular way to minimize the nastiness of url-bloat?
  • Build metrics given metadata, regex, patterns, template, configuration, etc

something like

server{0-5}.procfs.loadavg.OneMinute -> server0.procfs.loadavg.OneMinute, server1.procfs.loadavg.OneMinute, server2.procfs.loadavg.OneMinute, server3.procfs.loadavg.OneMinute, server4.procfs.loadavg.OneMinute, server5.procfs.loadavg.OneMinute server{0-5}.{pdc|sdc}.procfs.loadavg.OneMinute -> server0.pdc.procfs.loadavg.OneMinute, server1.pdc.procfs.loadavg.OneMinute, server2.pdc.procfs.loadavg.OneMinute, server3.pdc.procfs.loadavg.OneMinute, server4.pdc.procfs.loadavg.OneMinute, server5.pdc.procfs.loadavg.OneMinute server0.sdc.procfs.loadavg.OneMinute, server1.sdc.procfs.loadavg.OneMinute, server2.sdc.procfs.loadavg.OneMinute, server3.sdc.procfs.loadavg.OneMinute, server4.sdc.procfs.loadavg.OneMinute, server4.sdc.procfs.loadavg.OneMinute

Testing

  • test the heck out of it.
  • implement $httpBackend that emits graphite metrics
  • mock graphite service

Distribute new metrics using events

Module stats last updated: 2017-06-25 16:00:06

Disclaimer: Some data on this page may have been gathered from the authors GitHub respository. If you see any mistakes or outdated information please let us know. Thanks!