Install clustered On-premise version of Bugsnag.
If you have the Single Machine version of Bugsnag On-premise, please follow the single machine installation guide instead.
To get started with your Bugsnag On-premise installation, you’ll need the following things prepared in advance:
If you are installing Bugsnag On-premise on AWS please follow the CloudFormation installation guide.
Bugsnag On-premise uses Replicated Ship to perform and manage installations.
Run the following to initialize Bugsnag On-premise using Replicated Ship configuration tool. Make sure to run this command from a sensible directory as the tool will store configuration under
.ship folder in the current directory. This will contain the state of your installation including the configuration and therefore should be backed up.
docker pull replicated/ship && \ docker run -it -p 8800:8800 --rm -v `pwd`:/out \ -v /var/run/docker.sock:/var/run/docker.sock \ -e HTTP_PROXY -e HTTPS_PROXY -e NO_PROXY \ replicated/ship init \ "replicated.app/bugsnag-clustered"
You will be asked to enter your Bugsnag On-premise license. Enter the license you received from Bugsnag to continue to the next step.
The configuration tool will be available at
Follow the steps in the configuration tool and configure your installation as directed on the settings page. Once configured the next step will push all of the required images to your Docker registry and generate a
bugsnag-kubernetes.yaml file in your current directory with instructions on how to apply that to start Bugsnag.
It can take several minutes for Bugsnag On-premise to fully start up.
Now Bugsnag is running, you should be able to access the Bugsnag dashboard, where you’ll need to create your account and first project.
Visit your Bugsnag dashboard in a web browser to set up your account and create projects for each of the applications you wish to monitor.
Once you have created your account and first project you will need to configure your applications to send errors and sessions information to your Bugsnag instance instead of notify.bugsnag.com and sessions.bugsnag.com respectively. Follow the instructions on configuring platform notifiers for how to do this.