diff --git a/MAINTAINERS.yml b/MAINTAINERS.yml
index 6079a21eacbd2..45616072826cf 100644
--- a/MAINTAINERS.yml
+++ b/MAINTAINERS.yml
@@ -2893,6 +2893,19 @@ Input:
     - drivers.input
     - input
 
+Instrumentation Subsystem:
+  status: maintained
+  maintainers:
+    - fkokosinski
+    - tgorochowik
+  files:
+    - include/zephyr/instrumentation/
+    - samples/subsys/instrumentation/
+    - scripts/instrumentation/
+    - subsys/instrumentation/
+  labels:
+    - "area: Instrumentation"
+
 Intel Platforms (Agilex):
   status: maintained
   maintainers:
diff --git a/samples/subsys/instrumentation/README.rst b/samples/subsys/instrumentation/README.rst
index b522130cc19a4..a69bb136dbc4d 100644
--- a/samples/subsys/instrumentation/README.rst
+++ b/samples/subsys/instrumentation/README.rst
@@ -40,7 +40,7 @@ Alternatively you can run this using QEMU:
 
 After the sample is flashed to the target (or QEMU is running), it must be possible to
 collect and visualize traces and profiling info using the instrumentation CLI
-tool, :zephyr_file:`scripts/zaru.py`.
+tool, :zephyr_file:`scripts/instrumentation/zaru.py`.
 
 .. note::
    Please note, that this subsystem uses the ``retained_mem`` driver, hence it's necessary
@@ -48,10 +48,10 @@ tool, :zephyr_file:`scripts/zaru.py`.
    :zephyr_file:`./samples/subsys/instrumentation/boards/mps2_an385.overlay` for an example.
 
 Connect the board's UART port to the host device and
-run the :zephyr_file:`scripts/zaru.py` script on the host.
+run the :zephyr_file:`scripts/instrumentation/zaru.py` script on the host.
 
 Source the :zephyr_file:`zephyr-env.sh` file to set the ``ZEPHYR_BASE`` variable and get
-:zephyr_file:`scripts/zaru.py` in your PATH:
+:zephyr_file:`scripts/instrumentation/zaru.py` in your PATH:
 
 .. code-block:: console
 
diff --git a/scripts/zaru.py b/scripts/instrumentation/zaru.py
similarity index 100%
rename from scripts/zaru.py
rename to scripts/instrumentation/zaru.py