I've been tracking our observability spend with Claw pretty closely for the last quarter, trying to correlate daily deployment spikes with cost. We've got alerts set up in their billing API to warn us when daily ingestion goes over a certain threshold. The system has been working okay until this week.
Starting Monday, the dashboard numbers are completely out of sync with reality. Our actual usage from our own internal metric collection (we scrape our own volume stats) shows we had a major spike on Tuesday due to a misconfigured debug log level in a new service. However, the Claw "Current Spend" dashboard is still showing Monday's numbers, which were baseline. It's consistently about 48 hours behind. This makes proactive cost control impossible.
I've already tried the usual stuff:
* Refreshing the browser cache, using different browsers.
* Checking if it's a dashboard widget issue versus the main billing page—it's all delayed.
* Their API endpoints for billing metrics (`/v1/billing/usage`) are returning the same stale data.
This is a critical issue because their pricing model is based on daily volume, and without real-time or at least near-real-time data, we can't trigger our automated workflows to:
* Enable sampling rules in our OpenTelemetry collectors.
* Throttle certain verbose log sources.
* Switch to local debugging for suspect services.
Has anyone else run into this lag in the last few days? I'm trying to figure out if this is a widespread platform issue or something specific to our account. Their status page is all green, and support ticket response is, unsurprisingly, slow.
If you're also affected, what's your workaround? Are you relying on your own aggregated usage metrics to make decisions and just using Claw for the final bill reconciliation? I'm considering building a proxy that caches our own usage and triggers actions, but that defeats the purpose of paying for their integrated dashboard.
Automate everything. Twice.
Their billing API has always been eventual consistency. You can't build proactive controls on it. Your internal metric collection is the only real-time source you have, so just trigger your cost controls off that directly.
If you rely on a vendor's dashboard for financial ops, you're at the mercy of their batch jobs and reconciliation cycles. This isn't a bug, it's a design choice that saves them money.
Don't panic, have a rollback plan.