Navigating to the root will show the default view, if you want to include more metrics, you can specify in the query parameters (e.g: http://localhost:3000/?metrics=Iavg_A,Q1,P3) or tick the checkboxes on the right. When checking either "tooltip" or "plot" the app will fetch the relevant metrics for the current time range, downsampled if large enough. "Plot" is self-explanatory, "Tooltip" will include the values for that metric in the top left tooltip/overlay when hovering over points on the currently graphed metrics.
You can zoom in by selecting a range with the mouse or by entering the dates in the input boxes on the top right.
When the fetched points for the graph exceed a certain amount (1500), it will downsample using a LTTB algorithm, but every time you zoom in or out it will fetch data from the server again, and if the range is small enough you will see the actual data points.
Color sections on the default graph:
- yellow -> unloaded
- orange -> idle
- red -> loaded
Currently it starts marking as idle when Iavg_A > 1 and marking as loaded when > 30 but in case I got that wrong (specially I'm not sure about the upper idle limit) you can change the limits via query parameters, like so: http://localhost:3000/?idleLimit=80
The gantt chart at the bottom reflects the state changes of the machine over time at the zoom level of the timeseries above. Note that when a state group is too thin (as in one or a couple of points wide maybe) and the view is too zoomed out, the chart will display a blank space. Not sure how to solve this with the graph library I am using (highcharts).
Installs all dependencies
Will seed the database. The project uses mongodb, set the MONGO_URI environment variable via a .env file or otherwise prior to running this
Runs the project in development mode.
You can view the application at http://localhost:3000
The page will reload if you make edits.
Builds the app for production to the build folder.
The build is minified and the filenames include the hashes.
Runs the compiled app in production.
You can again view the application at http://localhost:3000
Runs the test watcher (Jest) in an interactive mode. By default, runs tests related to files changed since the last commit.
To debug the node server, you can use razzle start --inspect. This will start the node server and enable the inspector agent. For more information, see this.
To debug the node server, you can use razzle start --inspect-brk. This will start the node server, enable the inspector agent and Break before user code starts. For more information, see this.
If your application is running, and you need to manually restart your server, you do not need to completely kill and rebundle your application. Instead you can just type rs and press enter in terminal.