Skip to main content
The Miru Agent does not (currently) provide a command line interface. However, the agent can be managed using standard systemd commands and other standard Linux tools. The current CLI is only for managing Miru resources from your development machine’s terminal. Please do not attempt to use the miru command to manage the agent.

​
Version

To check the version of the agent, use the dpkg-query command with the miru-agent debian package. 
dpkg-query -W -f='${Version}\n' miru-agent

​
Logs

The Miru Agent logs are accessible via journalctl, the standard tool for viewing systemd service logs.

​
View all

By default, journalctl truncates each line’s output to the size of the terminal window. We recommend using the --no-pager flag to view the full log output for each line. 
journalctl -u miru --no-pager

​
Tail in real-time

Tail the logs and watch new entries as they appear. 
journalctl -u miru -f --no-pager

​
Recent logs

View only the most recent log entries (e.g., the last 100 lines). 
journalctl -u miru -n 100 --no-pager

​
Filter by time

View logs from a specific time period. 
# Logs from the last hour
journalctl -u miru --since "1 hour ago" --no-pager

# Logs from today
journalctl -u miru --since today --no-pager

# Logs from a specific date/time range
journalctl -u miru --since "2024-01-15 09:00:00" --until "2024-01-15 12:00:00" --no-pager

​
Filter by priority

View only logs of a specific priority level (e.g., errors). 
# Show only errors and above
journalctl -u miru -p err --no-pager

# Show warnings and above
journalctl -u miru -p warning --no-pager
Combine flags for more targeted output. For example, journalctl -u miru -f -n 50 --no-pager will tail the last 50 lines and then follow new entries in real-time.

​
Systemd

The Miru Agent runs as a systemd service named miru, allowing you to manage the service using standard systemctl commands. You can find the agent’s systemd service files on your file system at the following paths:
  • /lib/systemd/system/miru.service
  • /lib/systemd/system/miru.socket

​
Status

To check the status of the agent, use the status command. 
systemctl status miru
Depending on the state of the agent, you will see outputs similar to the following:
The agent is running as expected.

​
Restart

Restarting the agent stops and starts the agent, giving it a fresh start. If you’re experiencing unexpected behavior, restarting the agent is a good place to begin. 
systemctl restart miru
If the agent is not running, restarting it will start it.

​
Stop

stop stops the agent while leaving its state intact. Stopping the agent does not disable the agent—it will still automatically start on next system boot. Note that stopping the agent will prevent any new deployments from reaching the device until the agent is started again. 
systemctl stop miru
If the agent is not running, stopping it does nothing.

​
Start

start starts the agent if it has been stopped. 
systemctl start miru
If the agent is already running, starting it does nothing.

​
Disable

Disabling the agent prevents it from starting automatically on boot. This does not immediately stop the agent—it will still run if it is currently running. However, it will not be able to start on next system boot. 
systemctl disable miru

​
Enable

Enabling the agent allows it to start automatically on boot. This is the default behavior after installation and only needs to be done if the agent has been disabled. Enabling the agent will not immediately start it—it will still need to be started manually. 
systemctl enable miru