Hi, In the latest changelog of the `oakctl` tool I saw that there is an option for analytics: * Added analytics to **`oakctl`**. Analytics can be disabled with the **`OAKCTL_ANALYTICS=0`** environment variable. Is there more information about this analytical tool? Kind regards Ryan

Hi Ryan, We added usage analytics collection to `oakctl` in `v0.23.0`. We collect the following usage information: * oakctl command path: e.g. `oakctl.device.list` (without free text - for example `oakctl app exec ` doesn't include and ) * oakctl flags (without flag values) * Correlation id which we use to correlate multiple oakctl invocations to the same session. The id is not personal identifying information since it's randomly generated and rotated after 10min of inactivity. * comand validity * command invocation timestamp * Host architecture and OS family (macos, linux, windows) * oakctl version * Detection of coding agent usage: based on the presence of any of the environment variables: `AGENT, CLAUDECODE, CODEX_SANDBOX, CODEX_CI, CODEX_INTERNAL_ORIGINATOR_OVERRIDE, CURSOR_AGENT, CODEX_THREAD_ID, GEMINI_CLI, PI_CODING_AGENT` * oakctl command completion: timestamp, success (exit code == 0) All the best, Filip

oakctl analytics

RyanPaesschesooneVintecc

Hi,

In the latest changelog of the oakctl tool I saw that there is an option for analytics:

Added analytics to oakctl. Analytics can be disabled with the OAKCTL_ANALYTICS=0 environment variable.

Is there more information about this analytical tool?

Kind regards

Ryan

filipjeretina

Hi Ryan,
We added usage analytics collection to oakctl in v0.23.0.
We collect the following usage information:

oakctl command path: e.g. oakctl.device.list (without free text - for example oakctl app exec <id> <command> doesn't include <id> and <command>)
oakctl flags (without flag values)
Correlation id which we use to correlate multiple oakctl invocations to the same session.
The id is not personal identifying information since it's randomly generated and rotated after 10min of inactivity.
comand validity
command invocation timestamp
Host architecture and OS family (macos, linux, windows)
oakctl version
Detection of coding agent usage: based on the presence of any of the environment variables: AGENT, CLAUDECODE, CODEX_SANDBOX, CODEX_CI, CODEX_INTERNAL_ORIGINATOR_OVERRIDE, CURSOR_AGENT, CODEX_THREAD_ID, GEMINI_CLI, PI_CODING_AGENT
oakctl command completion: timestamp, success (exit code == 0)

All the best,
Filip

RyanPaesschesooneVintecc

Hi,

thanks for the response. This for better debugging on your side I assume.

Is there a way to get the device analytics (cpu/mem/disk usage) with oakctl?
Another question we have is changing the device from dhcp to static ip and vice versa with oakctl. Currently I have to log in via ssh and update it manually.

agentconfd configure 192.168.82.10,255.255.255.0,192.168.82.11 --dns 8.8.8.8
nmcli c modify static-eth0 ipv4.method manual
nmcli c down static-eth0 && sleep 1 && nmcli c up static-eth0

This is because there was a bug where the device would randomlly jump to link local. Is this still the case and can I update it with oakctl device setup?

Kind regards

Ryan

Oskar-Luxonis

Hey RyanPaesschesooneVintecc - oakctl doesn’t currently expose CPU, memory, or disk usage; for those you’d need to connect through SSH/ADB and inspect the device directly.

For networking, oakctl device setup can configure this during setup, but for an already configured device the supported route is agentconfd on the device: agentconfd configure <ip>,<netmask>,<gateway> for static IP, or agentconfd configure dhcp to revert to DHCP. Please avoid changing the NetworkManager profile manually.

The link-local address is the expected fallback when no DHCP server is available. We have also fixed an IPv4LL issue in newer OS releases; if you are on OS 1.20.5, please update before setting a static IP.

Docs: static IP / DHCP configuration

Thanks,
Oskar

RyanPaesschesooneVintecc

Oskar-Luxonis

Thanks for the answer, are device metrics on the roadmap?

Kind regards

Ryan

Oskar-Luxonis

RyanPaesschesooneVintecc - they are on roadmap, but sadly can't give you estimate time.
Will write to you when I get any updates.

Best,
Oskar