An administrator may be asked to collect diagnostic information on one of our main services. For example, ecs-ec. Commands such as: /opt/qradar/support/thredtop.sh /opt/qradar/support/jmx.sh These…

Question

Options

• Agrep JMXPORT /opt/qradar/init/*
• Bgrep JMXPORT /opt/qradar/systemd/env/*
• Cgrep JMXPORT /opt/qradar/system/bin/*
• Dgrep JMXPORT /opt/qradar/system/mem/*

• A
  2% (1)
• B
  92% (47)
• C
  4% (2)
• D
  2% (1)

Explanation

Option B is correct because in QRadar, service environment configurations - including JMX port assignments - are stored in environment files under /opt/qradar/systemd/env/, which is the systemd service environment directory where each service's variables like JMXPORT are defined. Option A is wrong because /opt/qradar/init/ contains legacy SysV init scripts, not environment variable definitions. Option C is wrong because /opt/qradar/system/bin/ holds executables, not configuration or environment files. Option D is wrong because system/mem/ is not a standard QRadar directory for service configuration at all.

Memory tip: Think "systemd = environment variables" - just as Linux systemd services load environment files (often via EnvironmentFile=), QRadar follows the same pattern by storing port variables like JMXPORT in systemd/env/. If you need a service's settings, look in the systemd environment folder.

No community discussion yet for this question.