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.

1. Monitoring web applications routes at scale.
2. Querying the monitored data in an interactive UI that is minimalistic to learn.
3. 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:

1. Updating the dependencies: make update
2. Executing the application (assuming all dependencies are installed): make run
3. Run UI (assuming all dependencies in dashboard/v1.1 are installed): make view-v1.1
4. Building the application for the current OS: make build
5. Testing Golang code: make test
6. Complete testing include building for all OSs out there: make test_complete
7. Cleaning up the residual files: make clean
8. (optional) Check linting (assuming golangci-lint is installed): make lint

1. Download Postman and Install it.
2. Create a new collection.

1. Add request
2. Select method GET
3. Copy and Enter below request url
   http://localhost:9990/service-state
4. Send the request to url.
5. This API returns the state of the services (active or passive) in real-time.

1. Add request
2. Select method GET
3. Copy and Enter below request url
   http://localhost:9990/routes-summary
4. Send the request to url.
5. 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!