BugSnag On-premise system requirements
You will install Replicated kURL on your server during installation of BugSnag On-premise. A set of minimum system requirements can be found in the kURL documentation. These are minimum requirements and you must ensure that your server also meets the additional requirements defined on this page.
BugSnag requires a minimum of 300GiB 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.
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.
kURL does not recommended that you configure the system with multiple mount points. kURL will use the following directories for storage - you should ensure these are configured prior to installation:
| Path | Use | Disk space required |
|---|---|---|
/var/openebs |
Local persistent volume (PV) provisioner | 20GB |
/var/lib/containerd |
Containerd is a Container Runtime Interface | 69GB |
/run/containerd |
Containerd is a Container Runtime Interface - this drive will be mounted as a temporary filesystem | 20GB |
/var/lib/kubelet |
Kubelet | 20GB |
/var/lib/kurl |
kURL | 4GB |
For most workloads, BugSnag requires 8 CPU cores.
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. We would also recommend considering our high availability installation.
BugSnag requires at least 32GiB 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.
The server running BugSnag must have a static internal network IP address and hostname.