Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Welcome to the M-Theory Dashboard- API Replacement Javascript Challenge- Part 2

In our previous challenge we changed some things to accomodate a new HTSQL REST endpoint.

In this challenge we'd like to really tear things up and change how the charts are being rendered. Currently, calculations for drawing the charts are being made in code. We'd like to push this work back on to our HTSQL service. For instance, when feeding the chart components data, we're calculating things like "Avg. CPU Consumption across all the servers". We'd like those average calculations to be put into the HTSQL call instead and remove all the in app calculations. This should be done on ALL charts in the app, both instant & historical.

We'd also like to add a filter to the app to toggle between east & west data centers.

In addition to this we've seen some odd buggy behaviours that we want to make sure gets addressed.

Requirement:

  • Replace all in app chart calculations with HTSQL calls. This should be done for both instant and history charts.
  • Add a dropdown to select which data center to filter on. This can be done on the "dcname" field. This selection will apply to all calls
  • some bugs we've noticed
    • Sometimes, on the instant charts, the graph data is incorrectly displayed. See attached screen shot.
    • The update time occasionally shows incorrect. See attached screen shot.

SETUP

  • Request access to the Gitlab repo group here by posting on the forums or email lazybaer .
  • Once added to the team, fork the repository and work off this branch.
  • All pertinent code can be found under the /public folder. Specifically, /public/js/common.js and /public/js/dashBoardData.js . The surrounding node application is for running locally (npm install & npm start) or deploying to Heroku.


Final Submission Guidelines

SUBMISSION:

  • Upload documentation for how to run your submission
  • Upload all your source code as a zip
  • Add lazybaer as members of your forked repository
  • Provide a video overview of your submission
  • Winner will be requried to submit a merge request on gitlab against the branch specified

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30050681