Watt 3 operations
Use the installed local CLI and its help output. Runtime IDs and application IDs are
different: discover them with wattpm ps and wattpm applications <runtime>.
| Goal | Reference |
|---|---|
| Start, stop, restart, reload, inject, import/resolve | CLI |
| Logs, traces, metrics | Observability |
| CPU/heap profiling and capacity | Performance |
| Scheduled tasks | Scheduler |
| Containers | Docker |
| Probes, scaling, rolling deployments | Kubernetes |
| Managed deployment | Cloud |
| Failures | Troubleshooting |
Build with the same lockfile and compatible Node.js version used for deployment. Preserve framework artifacts and production dependencies. Supply environment variables through the deployment platform; do not bake secrets into images or frontend bundles.
Measure actual health endpoints, startup time, termination behavior, worker memory, database pool usage, and cache behavior before increasing replicas or workers. Configuration and environment output can contain credentials; redact it in reports.
Stop processes started for diagnostics, keep profiles out of source control, and distinguish static review from commands actually run.