BugSnag On-premise system requirements
This page refers to BugSnag On-premise legacy single machine version 3. For the latest information please see BugSnag On-premise.
Replicated supports Linux-based servers that can run current versions of Docker. For more information check the supported operating systems page.
BugSnag requires a minimum of 200GiB to function in its data directory. Your exact storage size requirements will vary depending on the volume of events and size of those events. As an estimate we recommend allowing 4 GiB per million events stored to give yourself enough breathing room. If performing an airgapped installation, at least an additional 50GiB will also be required to store the airgap extraction.
A minimum of 50GiB free space is required on the root partition (/) for storing the BugSnag On-premise Docker images and containers.
The drive you use as your data drive should use a stable, performant file system like Ext4 or XFS if possible. An SSD is heavily recommended. Ideally this drive should also support filesystem snapshots, either through a virtualization layer (like EBS), or at the filesystem level using LVM snapshots or ZFS snapshots to make backups easier to manage.
BugSnag requires at least a dual-core CPU, and that will work for low volume installations where you expect sporadic crash volume. For anything more than that we recommend going with a quad-core CPU.
If you have high throughput applications sending events to your instance, you could find you need more cores. Your contacts at BugSnag can help you try to estimate your load.
BugSnag requires at least 16GiB of memory to function. Your memory requirements will be a function of how many events you are planning to search across, but for most customers 32GiB will be plenty.
If you are finding your dashboard is slowing down you will likely need more memory, or to reduce the number of events being stored in your instance.
We recommend that the server running BugSnag has a static internal network IP address.
BugSnag requires at least version 20.10.7 of Docker. Our installation scripts will help you install a suitable version of Docker if you don’t already have one.
From Docker 18.09, the Docker CLI and containerd.io are in separate packages and should be installed or updated at the same time as the Docker Engine. To ensure you are running a compatible version of containerd.io for your version of Docker, see the Docker release notes
We highly recommend using the overlay2 storage driver for Docker. You can verify which storage driver is currently configured by running the following command:
docker info | grep "Storage Driver"
Please follow the instructions here to configure Docker to use the overlay2 storage driver.
We recommend configuring the port range that Docker uses to assign dynamic ports to avoid port collisions with named ports:
Find out the current IP range, use the following command:
sysctl net.ipv4.ip_local_port_range
Then, set the upper range of local ports to 48999 by first stopping Docker then add the following to /etc/sysctl.conf:
net.ipv4.ip_local_port_range=XXXXX 48999
Load the settings by running:
sudo sysctl -p