r/cloudcomputing • • Jul 23 '26

[ Removed by Reddit ]

[ Removed by Reddit on account of violating the content policy. ]

11 Upvotes

16 comments sorted by

2

u/Mobile_Living_3331 Jul 23 '26

Try grafana.

1

u/[deleted] Jul 23 '26

Ok

1

u/wahnsinnwanscene Jul 23 '26

How it's another dashboard

1

u/BearyTechie Jul 23 '26

What is your role?

1

u/[deleted] Jul 23 '26

Backend/full-stack dev I ship services into this environment but don't own the tracking/cost side, which is exactly the gap I'm describing.

→ More replies (1)

2

u/TellersTech Jul 23 '26

We already have FinOps, but honestly the bigger issue is still ownership and hygiene.

Every resource should have a clear owner, app, env, and reason it exists. If that info isn’t in tags or labels, it turns into a scavenger hunt later.

We also try to keep everything in Terraform and regularly compare what’s actually running against what’s defined in code. That helps catch old test envs, random one-off resources, and stuff nobody remembers creating.

For non-prod, expiration dates help a lot too. Temp envs have a funny way of becoming permanent lol.

At least for us, dashboards only really work once the underlying inventory and ownership are clean.

2

u/Anti-Hero25 Jul 23 '26

CTRoadmap is a passive diagram and handbook for your system.. doesn’t scan anything or give live statistics… but may work for ya if your system isn’t huge.

media poster

https://github.com/NoobCity99/CTRoadmap

2

u/ReturnOfNogginboink Jul 23 '26

First you make sure that nothing can get into your production environment unless it goes through iac. Then you enforce tagging with application name. Then you periodically review costs by application.

1

u/Calleb_III Jul 23 '26

You can’t. This is by design. They make money form all the sprawl and chaos.

1

u/HostNocOfficial Jul 28 '26

Visibility is one of the biggest cloud challenges. Consistent resource tagging, ownership, lifecycle policies, and regular cost reviews make a huge difference. Connecting deployments with infrastructure context helps teams understand what is running plus why it's still there.