Haystack-ui is the web UI for haystack. It is the central place for visualizing processed data from various haystack sub-systems. Visualization tools in haystack-ui include -
- Traces - Distributed tracing visualization for easy root cause analysis
- Trends - Trends visualizing for vital service trends
- Service Dependency [coming soon] - Real time dependency graph with health and connectivity indicators
- Alerts and Anomaly detection [coming soon] - UI for configuring and subscribing alerts
Haystack-ui's navigation is pivoted around services. On selecting a service, you will get various visualizations tools each corresponding to a haystack sub-systems.
It is a expressjs based single page client side app written in ES6 + React and using Mobx for data flow.
Ensure you have node >= 8.6 and npm >= 5.3 installed.
This application uses webpack as the UI module bundler. To build + bundle all the required UI assets (CSS/JS) and run expressjs server, use:
$ npm install # install dependencies
$ npm run start:dev # start server in hot-reload server side
Once start is successful you can visit http://localhost:8080/
To continuously re-build the assets while you are developing, use this command in a separate terminal:
$ npm run watch
Haystack-ui utilizes Mocha as it's testing framework, with Chai as the assertation library, Enzyme for utility, and JSDOM as a headless browser for rendering React components. ESLint is used as a linter and insurance of code quality.
To run the test suite, enter the command npm test.
To check code coverage, run npm run coverage and open the generated index.html in the created coverage folder
Note- You may have to install Cairo dependencies separately for tests to work.
- OS X Users :
brew install pkg-config cairo pango libpng jpeg giflib - Others: Refer https://www.npmjs.com/package/canvas#installation
We have provided make commands to facilitate building. For creating docker image use -
$ make all
Haystack UI can be configured to use one or more stores, each providing user interface for one subsystem in Haystack. Based on what subsystems you have available in your haystack cluster, you can configure corresponding stores and UI will adapt to show interfaces only for the configured subsystems. For more details on this refer - https://github.com/ExpediaDotCom/haystack-ui/wiki/Configuring-Subsystem-Stores
If you have an existing zipkin cluster you can use haystack UI as a drop-in replacement for zipkin's UI. For more details on this refer - https://github.com/ExpediaDotCom/haystack-ui/wiki/Configuring-Subsystem-Stores#zipkin-store