Cost tracking
Costs roll up from:- Warehouse queries executed by Planasonix on your behalf (when telemetry is available from the warehouse)
- Managed compute for Planasonix-hosted runners or integrated clusters
- Egress and API charges where cloud billing APIs map usage to jobs
team, product, and env so finance can allocate spend fairly.
Connect billing sources
Admins link cloud billing exports or warehouse usage APIs in Settings → Compute / integrations (per deployment).
Validate attribution
Run a known test job and confirm its cost appears under the expected pipeline within 24–48 hours.
Usage analytics
Usage charts show CPU-hours, slot time, bytes scanned, or rows processed depending on the engine. Slice by schedule vs ad-hoc runs to see whether automation or manual previews dominate.- Engineers
- Managers
Find expensive nodes or queries to refactor first (wide scans before selective filters).
Optimization recommendations
Recommendations may suggest:- Cluster rightsizing for recurring jobs
- Partition pruning opportunities in SQL
- Caching or incremental patterns instead of full reloads
- Moving dev workloads to smaller warehouses
Some warehouses bill separately for storage; cost insights may focus on compute unless you integrate storage billing feeds.
Related topics
Compute settings
Configure execution environments that drive spend.
Usage and limits
Compare actuals to plan entitlements.