Every move on the cost line, named by what happened

The events that moved the organisation’s cost run rate over the last days UTC days (ankra cost events), newest first, in the caller’s display currency: application releases (version changes in the clusters’ resource graphs), node-count changes between adjacent priced hours, scheduled and manual stops and starts, executed cost decisions, clusters entering or leaving pricing, and resolved cloud waste. A snapshot-measured event carries window_delta_monthly_cents, how the cluster’s run rate moved between the priced hour before it and the first priced hour at least 30 minutes after it; delta_monthly_cents is set only when the event was alone in that window, no other event on the cluster being measured across any of its hours (delta_status isolated). Events whose windows overlap by any span, identical or not, are shared: each carries its window’s move and none claims a share of it. A start alone in a window whose run rate fell, or a stop alone in one whose run rate rose, is contradicted: something else moved it, so it carries the window’s move and no delta of its own. A node-count change alone in a window that moved against its count is read from the node types the metering recorded for its two hours: nodes of one type replacing another’s (or a spot or on-demand count moving against the node count) can move the run rate either way, so the move is its own (isolated) and the note names what changed; nodes only added across a falling run rate, or only removed across a rising one, are contradicted; and when the platform does not have every node’s type, spot or on-demand count for both hours it is node_types_unknown, carrying the window’s move and no delta of its own. metering_gap means the cluster was not priced for some hours inside the event’s window (a start after a stop it was not metered through, a missed metering hour): the run rate either side of the gap is no move of the event’s, so it carries neither delta, and an event whose window overlaps it is still shared. no_snapshots means no priced hour on one side, so the move is unknown, never zero. A coverage event’s delta is coverage, not spend; a resolved finding’s is its own monthly cost (own_cost), unknown (unpriced), or not_counted with no delta when other organisations also saw the resource and its cost counts in another organisation or in none. sources says which kinds could be read; a kind marked unavailable is missing from events, not quiet. At most 500 events (truncated). Bearer-PAT twin of the browser route of the same name under /org.