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
- Cost incident investigation
Cost incident investigation
Move a cost anomaly from detection through assigned investigation and closure.
Step by step
-
Detect Cloud Cost Analyst
Cloud Cost Analyst reviews a spend alert or anomaly against the daily charge.
- Identify the amount and source
- Updates Spend alerts, Cost anomaly events, Cloud cost lines
-
Acknowledge Cloud Cost Analyst
The assigned analyst marks the incident Acknowledged and records the response event.
- Record the response and owner
- Updates Incidents, Cost event log
-
Investigate Cloud Cost Analyst
The analyst checks the service, asset and cost line, then adds dated updates.
- Keep the dated investigation trail
- Updates Incidents, Incident updates, Assets
-
Recommend Service Owner
Service Owner records a saving recommendation when a corrective change is appropriate.
- Describe a proposed saving action
- Updates Optimization recommendations, Incidents
-
Resolve Cloud Cost Analyst
The analyst records the mitigation and marks the incident Resolved after checking the cause.
- Record mitigation and resolution
- Updates Incidents, Cost event log
-
Close Service Owner
Service Owner reviews the explanation and closes the incident.
- Confirm the final explanation
- Updates Incidents, Incident updates
Who does what
Roles and permissions- Cloud Cost Analyst
- , Service Owner, Finance Manager.
Set up Cloud Cost Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.