New Savings Proposals: approve, test and roll back cost changesLearn more Sign in|Talk to a cloud engineer
Product tourGet a demo

Cost alerts in the channel that owns them

Medium and high severity cost anomalies post to Slack. Anyone can share a recommendation to Slack or Microsoft Teams. Budgets, proposals, schedules and the weekly report still arrive by email.

Get a demoAll integrations
What you're watching
  1. 1
    A High alert lands in #cloud-cost-alerts

    Amazon EC2 in prod-core is at $8,912 against $6,240 expected, up 42.8%. The alert names the Checkout team and the checkout-api node group.

  2. 2
    The owner answers in thread

    Priya replies that she is scaling checkout-api back to 14 nodes after the load test. Teammates react in the channel.

  3. 3
    A recommendation is shared

    Ana Ruiz shares the checkout-api rightsizing recommendation to the channel, and Open in CloudLens takes the reader to the details.

Who does thisOn-call platform engineer and the Checkout team, with the FinOps lead sharing follow-up workWhat you getThe spike is seen and handled the morning it posts, in the channel the owning team already reads.

Alerts sent to a shared channel get muted

A cost spike or a critical finding has to reach the team that owns the resource, not a channel everyone ignores.

Alerting

Email alerts get buried

What usually happens: An anomaly email lands in a shared inbox on Tuesday. Someone reads it on Friday, after three more days at the higher rate.

How CloudLens resolves it: The alert posts to #cloud-cost-alerts with actual and expected spend, so the on-call engineer sees it that morning.

Resolved
Ownership

Owners never hear about it

What usually happens: The FinOps lead knows about a recommendation, but the team that runs the service never does.

How CloudLens resolves it: Post the recommendation to that team's Slack or Teams channel, with savings, effort and a link back to the details.

Resolved
Noise

Noisy channels get muted

What usually happens: A channel that pings on every small fluctuation is muted within a week. After that, real spikes go unseen too.

How CloudLens resolves it: Only medium and high severity anomalies post to Slack. Everything else stays on the Anomalies page.

Resolved

Hear about a spike the day it starts

Medium and high severity cost anomalies post to #cloud-cost-alerts with actual against expected spend, when it started and the main driver. From any recommendation, you can also post it to a Slack channel in two clicks.
  • Incoming webhook and channel
  • Medium and high anomalies
  • Post a recommendation
  • Test message
What you're watching
  1. 1
    Scroll back through the channel

    Earlier posts show a shared S3 recommendation marked Addressed and a medium Data Transfer anomaly in prod-data that was already resolved.

  2. 2
    Today's alert has the numbers

    The High alert shows actual and expected spend, start time, team and top driver, with View anomaly and Open Cost Explorer buttons.

  3. 3
    Recommendations post to the same channel

    A rightsizing recommendation shared by Ana arrives with savings, owner and effort. Open in CloudLens goes straight to it.

Who does thisPlatform engineer who set up the webhook, and the engineers who watch the channelWhat you getAnomalies and savings work for Checkout show up in one channel with enough detail to act on.

Share a recommendation with its owners

Connect an incoming webhook to Cloud Ops › Alerts and send a test message. After that, any recommendation can be posted to the channel with its savings, effort and owner, plus a link back to CloudLens.
  • Incoming webhook and channel
  • Post a recommendation
  • Test message
What you're watching
  1. 1
    A test message confirms the channel

    CloudLens posts a test to Cloud Ops › Alerts. It confirms that recommendations can now be posted there.

  2. 2
    Ana posts a recommendation

    The card shows the checkout-api rightsizing at $3,140 a month, Medium effort, owner Checkout, service EKS and status Not Started.

  3. 3
    The owner picks it up

    Someone opens it in CloudLens, and Priya replies that she is reviewing it and will add it to this sprint.

Who does thisOperations lead who connects the Teams webhook, and the service owners in that channelWhat you getThe team that runs checkout-api sees the recommendation where planned changes are tracked, with a link to the full detail.

A Tuesday morning cost spike

Lumora Retail's engineers work in Slack. The operations group lives in Microsoft Teams. Here is how one anomaly and one recommendation reached the right people.

DPDev PatelOn-call platform engineer, Lumora Retail

Lumora Retail is a fictional company. The people, names and numbers are sample data.

    1
    Tue 08:12High

    An anomaly posts to #cloud-cost-alerts

    EKS spend for the Checkout team has been above its expected range since the previous afternoon. The message shows actual against expected spend and the top driver.
    2
    Tue 08:30Investigating

    Dev opens it in CloudLens

    The link goes straight to the anomaly. Cost Explorer shows the increase came from a node group that scaled out for a load test and never scaled back in.
    3
    Tue 09:05Resolved

    The node group is scaled back

    The Checkout team confirms the load test finished and scales the group down. Dev marks the anomaly Resolved and adds a note for the weekly review.
    4
    Tue 11:40

    A recommendation goes to Teams

    While looking into it, Dev finds a rightsizing recommendation for the same service and posts it to Cloud Ops › Alerts, where the operations group tracks planned changes.
    5
    Thu 10:00

    The change goes through a proposal

    The Checkout lead adds the recommendation to a Savings Proposal. The approver gets an email, reviews the dry run in CloudLens and approves it for Saturday's window.
Spikes found on Friday instead of Tuesday?

Send anomaly alerts to your channel

Get a demo

Where each notification is sent

Chat is for alerts and sharing. Approvals for proposals and schedules happen in CloudLens, and the approver is notified by email.

Notification
Slack
Teams
Email
Cost anomaly alerts (medium and high)
✓
—
✓
Post a recommendation to a channel
✓
✓
—
Budget alerts
—
—
✓
Savings proposal created or applied
—
—
✓
Schedule created, approved or rejected
—
—
✓
Weekly cost report and digests
—
—
✓
Early accessApprovals in Slack and Teams. Approving proposals and schedules from chat is rolling out through Atlas Labs.

One webhook per channel

Add a webhook

Paste an incoming webhook URL and the channel name in Settings, under Integrations.

Send a test

A test message confirms the channel is connected before a real alert depends on it.

Share from a recommendation

Post from the recommendation's row or its detail drawer. The message links back to CloudLens.

FAQ

Yes. Each is configured separately, with its own webhook and channel.

No. Slack only receives medium and high severity anomalies. Lower-severity ones stay visible on the Anomalies page.

Not today. Approvals happen in CloudLens with an email to the approver. Chat approvals are in early access through Atlas Labs.

Ready to see CloudLens in action?

Connect a read-only AWS role or Azure service principal. We'll walk you through your bill, your security graph and the first things worth fixing.