Modern web applications can have routes ranging from a few to millions in numbers. This makes it tough to discover then condition and state of the such application at any given point. Bench-routes monitors the routes of a web application and helps you know about the current state of each route, along with various related performance metrics.
- Monitoring web applications routes at scale.
- Querying the monitored data in an interactive UI that is minimalistic to learn.
- Reporting in case of any abnormalities.
For installation instructions, please head-over to INSTALL.md.
We use make
for building and executing the program.
Follow the commands to make the development process easier:
- Updating the dependencies:
make update
- Executing the application (assuming all dependencies are installed):
make run
- Run UI (assuming all dependencies in
dashboard/v1.1
are installed):make view-v1.1
- Building the application for the current OS:
make build
- Testing Golang code:
make test
- Complete testing include building for all OSs out there:
make test_complete
- Cleaning up the residual files:
make clean
- (optional) Check linting (assuming golangci-lint is installed):
make lint
- Download Postman and Install it.
- Create a new collection.
- Add request
- Select method GET
- Copy and Enter below request url
http://localhost:9990/service-state
- Send the request to url.
- This API returns the state of the services (active or passive) in real-time.
- Add request
- Select method GET
- Copy and Enter below request url
http://localhost:9990/routes-summary
- Send the request to url.
- This API returns the list of all URLs/Routes that are being monitored for testing using the application.
For more information, regarding the APIs. Visit Bench-Routes.
- Aquib Baig ([email protected])
- Muskan Khedia ([email protected])
- Harkishen Singh ([email protected])
- Instant messaging: bench-routes/community
- Discussions (Recent): https://groups.google.com/forum/#!forum/bench-routes-discussion
Want to file a bug, request a feature, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues. Make sure you follow the guidelines before sending a contribution!