Production monitoring for distributed systems
Real-time monitoring customized to fit distributed applications in general, and your application's specific needs in particular.
Keep track of the health of your system's endpoints, monitor for any processing errors, send failed messages for reprocessing and make sure your specific environment's needs are met, all in one consolidated dashboard.
Setting up the project for development
Connecting to ServiceControl and ServiceControl Monitoring
The URLs for both services can be set in
ServicePulse.Host/app/js/app.constants.js under the constant
URL ACL Reservation
ServicePulse depends on a self-hosted webserver. In order to start the project a URL ACL reservation needs to be setup. Either run Visual Studio with Administrative privileges or run the following command to add the required URL ACL reservation:
netsh http add urlacl url=http://+:8081/ user=Everyone
Setting up package manager
ServicePulse uses npm and bower as package managers. For the solution to work dependencies needs to be downloaded before opening the ServicePulse website.
Install the following dependencies if you don't have them installed yet
- Git for Windows
Set development environment
- Open cmd window and navigate into
npm installto install all the npm dependencies
- run the following command
npm run dev. This script will use webpack configuration to finish ServicePulse's required configuration, start watching root folder for changes, and it will host a dev server on port 8080
npm run dev fails with an error related to git submodule not properly configured, run the
npm install command again to ensure all required dependencies are available, and then run
npm run dev.
After doing the above steps one can open Visual Studio or your IDE of choice and continue working on this project. The site will be served for debugging at
Provided npm scripts
test- runs js tests in ServicePulse.Host.Test project
setup- this command runs few commands
- installs the npm packages
load- this command does the same thing that
setupbut webpack is run only once to produce artifacts. This command is used by the builder
serve- serves js artifacts using
webpack- runs webpack command, which does the following things for the given modules (monitoring, configuration)
- joins js together
- runs babel transpiler
- has a file watcher to run the above whenever file is saved
lint- checks with eslint all js files
dev- runs in parallel two scripts
NOTE: Webpack observes files and updates the artifacts whenever they are changed, however at the moment not every bit of code is processed by webpack. Only monitoring and configuration is.
Configuring automated tests
For information how to run automated tests please follow ServicePulse.Host.Tests/Readme.
Supported browser versions
ServicePulse is supported on the following desktop browser versions: