Minimum SDK version
Java SDK: 1.44.0 or higher
Supported runtime versions
For a complete list of supported Java versions, see the Java SDK compatibility documentation.
SSI uses the
--enable-native-access=ALL-UNNAMED flag on Java 24+ to enable native access for all code on the class path. This is necessary for products such as Profiling, which requires native access. See
JEP 472 for more information.
Limitations
By default, SSI does not instrument some Java applications and libraries to avoid performance overhead or non-actionable traces. These exclusions are defined in the Java SDK denylist. If your workload is included, SSI skips loading the Java SDK.
Known issues
Environment variable length: If your application uses extensive command-line options or environment variables, you might encounter initialization failures. This typically occurs when you have many JVM arguments or other startup configurations. To resolve this:
- Minimize non-essential JVM arguments
- Consider moving some configurations to a
.properties file - Check application logs for specific initialization errors
Minimum SDK version
Python SDK: 2.20.1 or higher
Supported runtime versions
Minimum Python version: 3.7 or higher
For a complete list of supported Python versions, see the Python SDK compatibility documentation.
Operating system considerations
Python 3.7+ is available by default only on:
- CentOS Stream 8+
- Red Hat Enterprise Linux 8+
For other distributions, you may need to install Python 3.7+ separately.
Minimum SDK version
Ruby SDK: 2.5.0 or higher
Supported runtime versions
For a complete list of supported Ruby versions, see the Ruby SDK compatibility documentation.
Operating system requirements
- Requires Linux distributions using glibc 2.27 or newer
- Not compatible with Alpine Linux or other musl-based distributions
Known issues
Uninstalling SSI: When uninstalling Single Step Instrumentation from a Ruby application, follow these steps to prevent errors:
- Before uninstalling: Make a backup of your
Gemfile and Gemfile.lock. - After uninstalling, do one of the following:
- Restore your original
Gemfile and Gemfile.lock. - Run
bundle install to rebuild your dependencies.
Minimum SDK version
Node.js SDK: 4.0 or higher
Supported runtime versions
For a complete list of supported Node.js versions, see the Node.js SDK compatibility documentation.
Operating system considerations
Supported Node.js versions are available by default only on:
- CentOS Stream 9+
- Red Hat Enterprise Linux 9+
For other distributions, you may need to install Node.js separately.
Limitations
- ESM modules: Instrumentation of ESM (ECMAScript modules) is not supported.
Minimum SDK version
.NET SDK: 3.7.0 or higher
Supported runtime versions
SSI supports both .NET Core and .NET Framework runtimes. For a complete list of supported versions, see:
Minimum SDK version
PHP SDK: 1.6.0 or higher
Supported runtime versions
For a complete list of supported PHP versions, see the PHP SDK compatibility documentation.
Limitations
SSI automatically disables when it detects:
- PHP’s Just-In-Time (JIT) compilation
- Any of the following extensions:
- Xdebug
- ionCube Loader
- NewRelic
- Blackfire
- pcov
If you need to run SSI alongside these tools, you can force it to enable by setting DD_INJECT_FORCE=true.
