These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Cloud Cost Management
- Process
- Data intake
Data intake
Trace provider events through ingestion, freshness checks and exports.
Step by step
-
Receive Cloud Operations Engineer
Cloud Operations Engineer checks the integration receipt and external event ID.
- Identify the provider event and endpoint
- Updates Integration receipts, Billing API endpoints
-
Process Cloud Operations Engineer
The engineer checks the ingestion run and its pipeline outcome.
- Establish the run outcome and resulting charges
- Updates Cost ingestion runs, Cloud cost lines
-
Check freshness Cloud Operations Engineer
The engineer reviews the source check time, success result and latency.
- Confirm the source period is current
- Updates Data freshness checks, Services
-
Review exceptions Cloud Operations Engineer
Rejected receipts and failed runs are examined before an analyst relies on charges.
- Trace rejection and window volume
- Updates Integration receipts, Usage windows
-
Export Cloud Operations Engineer
The engineer records export size, completion and validation for downstream use.
- Record validation of an extract
- Updates Data export runs, Cost data stores
Who does what
Roles and permissions- Cloud Operations Engineer
- , Cloud Cost Analyst, Admin.
Set up Cloud Cost Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.