- Always simulate and log
--costbefore sending transactions. - Use RPC
getFeeStats()to set inclusion fee (p90 recommended under load).
- Distribution of resource fees per function
- Average read/write entries and bytes per function
- Event+return sizes (aim << 8 KB cap)
- Oracle call failure rates and retries
- Spike in write-bytes or write-entries
- Repeated tx failures due to under-estimated event/return size
- Inclusion fee surge vs baseline
- Per-endpoint cost over time
- Top costly calls and scenarios
- WASM size trend per release
- If costs climb due to strings: enforce length caps at API layer and/or contract validation.
- If claim/resolve costs spike: batch payouts off-chain via token escrows or staged claims.