prometheus/web/ui/react-app
Julius Volz 3470ee1fbf
Make React UI the default, keep old UI under /classic (#8142)
The React app's assets are now served under /assets, while all old
custom web assets (including the ones for console templates) are now
served from /classic/static.

I tested different combinations of --web.external-url and
--web.route-prefix with proxies in front, and I couldn't find a problem
yet with the routing. Console templates also still work.

While migrating old endpoints to /classic, I noticed that /version was
being treated like a lot of the old UI pages, with readiness check
handler in front of it, etc. I kept it in /version and removed that
readiness wrapper, since it doesn't seem to be needed for that endpoint.

Signed-off-by: Julius Volz <julius.volz@gmail.com>
2020-11-03 14:51:48 +01:00
..
public react updates for pathPrefix (#7979) 2020-10-22 17:22:32 +02:00
src Make React UI the default, keep old UI under /classic (#8142) 2020-11-03 14:51:48 +01:00
.eslintrc.json Unify react fetcher components (#6629) 2020-02-03 15:14:25 +01:00
.gitignore Integrate beginning of React UI (#5694) 2019-10-17 14:38:09 +02:00
package.json Bump various react versions (#7820) 2020-08-22 21:02:50 +02:00
README.md Add the "assets" make target and change directory note in readme (#7908) 2020-09-16 15:01:48 +02:00
tsconfig.json ReactUI: folder re-organization (#6601) 2020-01-14 19:34:48 +01:00
yarn.lock web/ui/react-app/yarn.lock: Update UI dependencies 2020-10-08 09:32:17 +02:00

Working with the React UI

This file explains how to work with the React-based Prometheus UI.

Introduction

The React-based Prometheus UI was bootstrapped using Create React App, a popular toolkit for generating React application setups. You can find general information about Create React App on their documentation site.

Instead of plain JavaScript, we use TypeScript to ensure typed code.

Development environment

To work with the React UI code, you will need to have the following tools installed:

NOTE: When using Visual Studio Code, be sure to open the web/ui/react-app directory in the editor instead of the root of the repository. This way, the right ESLint and TypeScript configuration will be picked up from the React workspace.

Installing npm dependencies

The React UI depends on a large number of npm packages. These are not checked in, so you will need to download and install them locally via the Yarn package manager:

yarn

Yarn consults the package.json and yarn.lock files for dependencies to install. It creates a node_modules directory with all installed dependencies.

NOTE: Remember to change directory to web/ui/react-app before running this command and the following commands.

Running a local development server

You can start a development server for the React UI outside of a running Prometheus server by running:

yarn start

This will open a browser window with the React app running on http://localhost:3000/. The page will reload if you make edits to the source code. You will also see any lint errors in the console.

Due to a "proxy": "http://localhost:9090" setting in the package.json file, any API requests from the React UI are proxied to localhost on port 9090 by the development server. This allows you to run a normal Prometheus server to handle API requests, while iterating separately on the UI.

[browser] ----> [localhost:3000 (dev server)] --(proxy API requests)--> [localhost:9090 (Prometheus)]

Running tests

Create React App uses the Jest framework for running tests. To run tests in interactive watch mode:

yarn test

To generate an HTML-based test coverage report, run:

CI=true yarn test --coverage

This creates a coverage subdirectory with the generated report. Open coverage/lcov-report/index.html in the browser to view it.

The CI=true environment variable prevents the tests from being run in interactive / watching mode.

See the Create React App documentation for more information about running tests.

Linting

We define linting rules for the ESLint linter. We recommend integrating automated linting and fixing into your editor (e.g. upon save), but you can also run the linter separately from the command-line.

To detect and automatically fix lint errors, run:

yarn lint

This is also available via the react-app-lint-fix target in the main Prometheus Makefile.

Building the app for production

To build a production-optimized version of the React app to a build subdirectory, run:

yarn build

NOTE: You will likely not need to do this directly. Instead, this is taken care of by the build target in the main Prometheus Makefile when building the full binary.

Integration into Prometheus

To build a Prometheus binary that includes a compiled-in version of the production build of the React app, change to the root of the repository and run:

make build

This installs npm dependencies via Yarn, builds a production build of the React app, and then finally compiles in all web assets into the Prometheus binary.