Jakub Novák
e34d69525f
# Description Expose sandbox metrics in SDKs and CLI ``` e2b sbx mt il98ycmohc6enybi79uf8 Metrics for sandbox il98ycmohc6enybi79uf8: [2025-07-25 14:05:55Z] CPU: 8.27% / 2 Cores | Memory: 31 / 484 MiB | Disk: 1445 / 2453 MiB [2025-07-25 14:06:00Z] CPU: 0.5% / 2 Cores | Memory: 32 / 484 MiB | Disk: 1445 / 2453 MiB [2025-07-25 14:06:05Z] CPU: 0.1% / 2 Cores | Memory: 32 / 484 MiB | Disk: 1445 / 2453 MiB [2025-07-25 14:06:10Z] CPU: 0.3% / 2 Cores | Memory: 32 / 484 MiB | Disk: 1445 / 2453 MiB ``` --------- Co-authored-by: Tomas Valenta <valenta.and.thomas@gmail.com>
E2B Web App
This repository contains E2B Dashboard, documentation, and SDK references.
SDK References
The SDK references are generated from the source code in the packages folder.
Each package has its own SDK reference generator found in {package-dir}/scripts/generate_sdk_ref.sh, it generates markdown files with the following schema: ./src/app/(docs)/docs/sdk-reference/{package-name}/{version}/{module-name}/page.mdx.
When pushed to main, a github workflow checks for diffs in the packages folder, and if any are found, the SDK reference generator is run and the result is auto-commited the incoming branch.
Finally, when building or running the dev server, a prebuild step is run beforehand to generate the SDK reference TOCs and routes in the sdk-reference directory. This can also be run manually using npm run prebuild.
note: sometimes you may see uncommited changes or untracked files in the sdk-reference directory, this is fine and the files can be ignored.