bizzabo / new-relic-boxes Goto Github PK

License: MIT License

HTML 24.52% JavaScript 65.60% CSS 8.94% Shell 0.94%

new-relic-boxes's Introduction

New Relic Boxes

New Relic Boxes is an html5 dashboard for your R&D team. Boxes lets you monitor your applications and servers on New Relic. Alarm is played when one of your application / servers health status is changed.

Installation

Ensure node ^0.10.33 is installed and on your path.
Run npm install bower to install bower
Run bower install to install libraries
Run npm install to install dependencies
Run index.html (the easiest way) or run npm start to start a static server

Setup

press settings and add the following information:

Your new relic apikey (mandatory).

Your company name (optional).

Your favicon url (optional).

Your new relic account id (optional) - to open a new tab with your specific box on new relic app.

new-relic-boxes's People

Contributors

Stargazers

Watchers

Forkers

dz0ny nickcanz buckett samuraicode yujinqiu buzzedword smoya psalvitti bryant1410

new-relic-boxes's Issues

Automate angular style-guide rules with JSCS

Should help to make #14 more automatic, and could probably be piped into a travis build.

Create cross-platform static server

Most likely using nodemon (see https://github.com/johnpapa/ng-demos/blob/5a5e1b94f4280ce5d8397a6cb6b416b031107c08/modular/gulpfile.js#L364-L400). Need a single way to spawn servers.

Question:

Should common PaaS bootstrappers be part of this, or just a gulp task for local usage?

Chrome: net::ERR_BLOCKED_BY_CLIENT

I am on OSX 10.10 using Chrome 43.0.2357.81 (64-bit) and I am unable to load any data from New Relic

CSS Build Process

Just wanted to create an item in here to gauge interest level.

Because of #7, the gulpfile.js is going to become a bit more defined soon to account for the JS processing. The CSS in this project is pretty clear already, and I was wondering if you wanted any kind of tooling to wrap it.

We have options such as:

Preprocessors

LESS
SASS
Stylus

Postprocessors

PostCSS
- Autoprefixr
- Nesting
- CSS4

Or, honestly, just a "get off my lawn, concat it all, go away" approach. Anything here is fine, I just wanted to get an idea of what you had in mind moving forward-- I can tool any number of them up for you.

Build test harness around discrete functionality

Still sorting out the best way to accomplish this, I'm thinking stubbing out a New Relic response for multiple states would be the best way to test it all, and wrapping it with some Karma runners. Protractor would only be required to test the modal state (entering it, entering information, closing) -- that might be better suited for after initial units have been created.

Document parseData a bit for more transparency

Could you wrap a few inline comments around

new-relic-boxes/app/js/main.js

Lines 31 to 73 in bce636c

 $scope.parseData = function (data, pollerType) { 

 var shouldAlert = false; 

 $scope.size[pollerType] = data.length; 

 _.each(data, function (res) { 

 res.name = res.name.toLowerCase(); 

 var findByGroupName = function(group) { 

 return (res.name.indexOf(group.type) > -1); 

 }; 

 var groupSelected = _.find($scope.config.grouping, findByGroupName) || $scope.config.defaultGroup; 

 res.name = $.trim(res.name.replace(groupSelected.type, '').replace('-',' ')); 

 if (!$scope[pollerType][groupSelected.type]) { 

 $scope[pollerType][groupSelected.type] = { 

 data: {}, 

 name: groupSelected.type, 

 rank: groupSelected.rank 

 }; 

 } 

 var data = $scope[pollerType][groupSelected.type].data; 

 var currentStatus = $scope.healthCheckRank[res.health_status] || 0; 

 var previousData = data[res.name] || {}; 

 var previousStatus = $scope.healthCheckRank[previousData.health_status] || 0; 

 var status = (currentStatus - previousStatus); 

 $log.debug('status', status); 

 if (groupSelected.alarm && (status > 0)) { 

 shouldAlert = true; 

 } 

 data[res.name] = res; 

 }); 

 if (pollerType === 'servers') { 

 $scope.counter++; 

 } 

 if (shouldAlert) { 

 $scope.playAlarm(); 

 } 

 };

to clarify what this method is doing step by step? I could probably break it down a bit more into services if it was a bit less opaque, and make it more testable.

Pagination for newrelic API output

Because we have more than 200 non-reporting servers, i can only see non-reporting servers in my dashboard, even if I filter with the widget. This is because newrelic API uses pagination for the output. (My resultset is ~500 servers).

I'm not an expert in node, so I'm not able to contribute more than just add this issue. I'm sorry.

More info: https://docs.newrelic.com/docs/apis/rest-api-v2/requirements/pagination-api-output

Create build job for javascript files

Should do:

Concatenating all vendored files
Concatenating all application files
Auto-annotating angular functions

Unrelated, but should also set angular to ng-strict mode.

Bring all angular versions to minimum ~1.3

There's a discrepancy between some angular components and the base angular version at 1.2 and 1.3. Suggestion bringing it all up to 1.3 for version parity. Any particular reason why 1.2 was selected?

	$scope.parseData = function (data, pollerType) {
	var shouldAlert = false;
	$scope.size[pollerType] = data.length;
	_.each(data, function (res) {
	res.name = res.name.toLowerCase();
	var findByGroupName = function(group) {
	return (res.name.indexOf(group.type) > -1);
	};
	var groupSelected = _.find($scope.config.grouping, findByGroupName) \|\| $scope.config.defaultGroup;

	res.name = $.trim(res.name.replace(groupSelected.type, '').replace('-',' '));

	if (!$scope[pollerType][groupSelected.type]) {
	$scope[pollerType][groupSelected.type] = {
	data: {},
	name: groupSelected.type,
	rank: groupSelected.rank
	};
	}

	var data = $scope[pollerType][groupSelected.type].data;
	var currentStatus = $scope.healthCheckRank[res.health_status] \|\| 0;

	var previousData = data[res.name] \|\| {};
	var previousStatus = $scope.healthCheckRank[previousData.health_status] \|\| 0;

	var status = (currentStatus - previousStatus);
	$log.debug('status', status);
	if (groupSelected.alarm && (status > 0)) {
	shouldAlert = true;
	}
	data[res.name] = res;
	});

	if (pollerType === 'servers') {
	$scope.counter++;
	}


	if (shouldAlert) {
	$scope.playAlarm();
	}
	};