Every month, somewhere, a CFO sends this message:
"Our AWS bill was 30% higher. What happened?"
And somewhere, a DevOps engineer opens 4 tabs:
- AWS Cost Explorer
- GitHub deploy history
- PagerDuty or incident Slack channel
- CloudWatch metrics
Then spends 2-4 hours manually connecting the dots.
The answer usually turns out to be something like: "Tuesday's deploy
caused an error spike, triggered autoscaling, 11 instances spun up
and never terminated."
That's a 10-minute cause with a 4-hour explanation.
I'm building a tool called SIGNAL that watches these data sources
together and posts the correlation to Slack automatically — plain
English, no dashboard required.
Currently in early development and looking to talk to DevOps engineers
who've felt this pain. If this is a recurring problem for your team,
I'd love 15 minutes of your time.
Drop a comment or DM me.
Top comments (0)