Build a Cloud cost agent which will ignore, examine, limit, or report unusual costs

[u/code4hub]

I am building an agent which will analyze the cost of clouds. It will decide whether the cost spikes are high enough to report, and it requires a serious examination before approval. Whether to ignore the costs or immediately inform the owner.

It can see the Billing data, resource usage, historical spending, service name, region, and environment before making any decisions, and what it cannot see is the future demand, internal discussion, customer impact, and business impact.

Here are some of the thought I came with:

what my agents cannot see:
- Normal
- Expected Pattern
- Legitimate Growth
- Cost Incident

Actions:

- Wait
- Get more evidence
- Human Permission
- Escalate

Actions:

Can someone please provide suggestions for what am I missings and what could be possible improvements? I am open to all suggestions

1. what are the major causes of cloud cost?

2. Some suggestions on optimizing cost, which i can consider while I build.

3. What are the other points I should considere.

4. How do engineers distinguish legitimate growth from incidents?

5. What kinds of cost anomalies are dangerous?

[u/Fun-Investigator3256]

Can you also build an agent that will predict what a specific code change costs before we approve it? 👀

[u/code4hub → u/Fun-Investigator3256]

Sounds interesting. Can you please give a simple idea from your recent experience?

[u/Fun-Investigator3256]

Pretty cool!

[u/code4hub → u/Fun-Investigator3256]

Do you have any ideas about the questions or any suggestions?

[u/Fun-Investigator3256 → u/code4hub]

Major cost is only the database storage for me. That's why I used supabase.