Splunk® Enterprise

Workload Management

Splunk Enterprise version 9.0 will no longer be supported as of June 14, 2024. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk® Enterprise. For documentation on the most recent version, go to the latest release.

Set up Linux for workload management

Before you can configure workload management in Splunk Enterprise, you must set up cgroups on your underlying Linux operating system. How you set up cgroups for workload management depends on whether your Linux system is running systemd. To determine if your system is running systemd, see Is Linux running systemd?.

Workload management supports Linux cgroups v1 only. If your Linux system has been upgraded to a version running cgroups v2, you must revert your system to cgroups v1 to use Workload Management in Splunk Enterprise. For additional guidance and resources, see Workload Management operation during the transition to cgroups v2.

Is Linux running systemd?

Use one of the following options to determine if your Linux distribution is running systemd.

Option 1: Check systemd version

Run the systemctl command to check for a systemd version number.

$ systemctl --version
systemd 219
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

Workload management supports systemd version 219 or later. See System requirements.

Option 2: Check for systemd process ID

Run the following command to check for a systemd process ID. On most Linux systems, if the output shows PID=1, then you are running systemd. For example:

$ pidof systemd 
1

On Debian-based systems, /sbin/init is symlinked to /lib/systemd/systemd. As a result, the pidof command returns a number other than 1. For example:

$ pidof systemd 
5447

To confirm that a Debian-based system is running systemd, run the following command:

$ ps -q 1 ax
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:13 /sbin/init

The output shows a value of /sbin/initunder the COMMAND column. Now run the following command to check if /sbin/init is symlinked to /lib/systemd/systemd:

$file /sbin/init
/sbin/init: symbolic link to /lib/systemd/systemd

The output shows that /sbin/init is symlinked to a file called /lib/systemd/systemd, confirming that your system is running systemd.


To configure cgroups on Linux systems running systemd, see Configure systemd distributions for workload management.

To configure cgroups on Linux systems not running systemd, see Configure non-systemd distributions for workload management.

Last modified on 13 September, 2024
System requirements   Configure Linux systems running systemd

This documentation applies to the following versions of Splunk® Enterprise: 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.0, 9.2.1, 9.2.2, 9.2.3


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters