System requirements of a single-node deployment

View the system requirements of Self-Hosted Standard Edition on a single-node cluster.

Supported platforms and operating systems

Make sure you have a host on which you can run the Self-Hosted Standard Edition installer.

The host can be a new virtual machine or a dedicated physical machine. The Self-Hosted Standard Edition must not co-exist with a Self-Hosted Classic Edition (Docker).

Instana supports the following platforms and operating systems for the host:

Table 1. Supported operating systems
Platform Operating system
Linux® x86_64 Red Hat® Enterprise Linux® (RHEL) 9 and 8
Ubuntu 24.04, 22.04, 20.04, and 18.04
Debian 12, 11, and 10
CentOS Stream 9
Amazon Linux 2023
Oracle Linux 9
SUSE Linux Enterprise Server (SLES) 15 SP5
Linux® arm64 Supported on AWS GravitonExternal link icon. Deployment on other operating systems on arm64 is not tested.

Hardware requirements

The host must meet the CPU, memory, and storage minimum requirements.

CPU and memory requirements

Instana provides two installation types that you can set during installation. Pick an installation type based on your environment. The default installation type is demo.

  • Use demo installation type only for test and demo environments.
  • Use production installation type for production environments.

After you install Standard Edition, you cannot convert or migrate from demo installation type to production installation type.

The number of supported managed virtual servers (MVS) or hosts depend on several factors. To support more than 1500 MVS or hosts, you might need to consider Self-Hosted Custom Edition (Kubernetes or Red Hat OpenShift Container Platform) as it provides more options to scale and provides more high-availability and redundancy.

Some optional features might need more CPU and memory. Table 1 and Table 2 provide the CPU and memory requirements of the two installation types and the following optional features. If you plan to enable these optional features, it is ideal that you provide the CPU and memory that they need to avoid performance issues.

For more information about all the optional features that you can install, see Enabling optional features.

If you are enabling Self monitoring of your Standard Edition host, you need additional CPU and memory as shown in Table 2.

Table 2. CPU and memory requirements of demo installation type
Installation type
or feature
Number of CPU cores Memory (GB)
demo 16 64
Automation framework 1.2 4.8
Analyze logs 2 8
Business monitoring 1 4
End-user monitoring 1 4
Self monitoring 1 2
Synthetic monitoring 1.5 6
Table 3. CPU and memory requirements of production installation type
Installation type
or feature
Number of CPU cores Memory (GB)
production 24 96
Automation framework 1.5 6
Analyze logs 3 12
Business monitoring 1.5 6
End-user monitoring 2 4.5
Self monitoring 1 2
Synthetic monitoring 2 8

Storage requirements

The total storage requirement depends significantly on the infrastructure and workload that you plan to monitor. Furthermore, optionally used features such as Logging and Synthetics affect the required storage capacity.

Instana uses the following four directories for data storage. Due to the high data throughput of various Instana features, separate and fast storage volumes are required for each of the four directories.

  • Data directory for Elasticsearch, PostgreSQL, and Kafka data stores.
  • Metrics directory for Cassandra and BeeInstana data stores.
  • Analytics directory for ClickHouse data store.
  • Objects directory for raw spans, Synthetic monitoring, and End-user monitoring (EUM).

To avoid performance issues, use fast, dedicated storage such as solid-state drives (SSDs) and use separate disks for each directory.

The disk storage speed requirements measured as input/output operations per second (IOPS) are shown in the following table:

Table 4. Disk IOPS requirements
Installation type Required Preferred
demo 3000 6000
production 6000 9000

The following table provides the storage volume requirements of each installation type:

Table 5. Storage volume requirements
Installation type Root directory (GB) Data directory (GB) Metrics directory (GB) Analytics directory (GB) Objects directory (GB) Total storage volume (TB)
demo 100 150 300 500 250 1.28
production 100 500 1000 1200 1000 3.78

If variable data (/var) and home ($HOME) directories are mounted on separate disks, refer to the following table for the minimum required free space for each installation type.

Table 6. Root directory requirements
Installation type /var directory (GB) $HOME directory (GB)
demo 60 40
production 60 40
Note:

In an air-gapped environment, you need 20 GB more disk space in the directory where you create the air-gapped package, both on the bastion host and the Instana host. For more information about the package, see Creating the air-gapped installation package.

For about a month, you must monitor the storage volume that you initially assigned. You can then increase the capacity if necessary. Also, if you use more agents or enable more optional features, you must monitor the memory usage.

Networking requirements

The following ports on your host must be open and accessible. For more information about opening these ports, see Firewall rules.

Table 9. Required ports
Port number Direction Protocol Source Description
22 Inbound TCP External Port required for Secure Shell (SSH) connection (required only if you want to log in SSH)
80 Inbound TCP External HTTP protocol for Instana console UI
443 Inbound TCP External HTTPS protocol for Instana console UI
443 Outbound TCP External Required only in online environments. For more information, see Outbound network access requirements for self-hosted Instana deployments.
8443 Inbound TCP External Agent acceptor port
all Inbound TCP/UDP 10.42.0.0/16 and 10.43.0.0/16 Subnets of the self-hosted Instana components
all Inbound TCP/UDP Loopback Open the ports to allow a VM to send and receive its own data packets.

See the following notes:

  • External source means that the port must be accessible from outside of the Instana self-hosted enterprise (private) network.
  • IP addresses 10.42.0.0/16 and 10.43.0.0/16 must be able to access all ports (1 - 65535) internally.
  • The firewall must trust all traffic from the loopback address.
  • Port 443 outbound is needed for accessing certain repositories. For more information, see Outbound network access requirements.

What's next

Proceed with preparing your environment.