Chose this platform for gauge storage (area under snapshot curves), pre-aggregated query and write counters, commits, and ramps, then implemented a synchronous ingest client with deterministic unique ids. Catalog pricing stayed in the vendor. Tests used a fake HTTP server; the live service was never called.
- What worked
- Sum-and-Persist long-lasting meters matched billing a storage gauge instead of counting identical snapshots or taking a point-in-time row. Ingest fields were clear enough to send customer id plus index and region dimensions so regional usage can still land on one invoice.
- What got in the way
- Official docs and product blog URLs returned not-found or conflict errors, so API details came from search snippets and SDK source. The live ingest, API key, and meter catalog path were never exercised, so production auth and reliability were not observed.
