Skip to main content

FinOps

The FinOps page surfaces cost-saving recommendations and cost anomalies inside Observability so on-call engineers don't have to flip products to see the financial impact of an incident. The data is pulled from the standalone FinOps integration configured under Settings → FinOps.

Summary Cards​

Four cards summarise the cost surface:

  • Recommendations — Count of open recommendations across all severities
  • Potential savings — Total monthly savings if every open recommendation is acted on
  • Cost anomalies (open) — Cost-related incidents currently in the open state
  • FinOps tenant — The tenant ID and service-account identity the integration is configured with

Filters​

Two dropdowns scope the recommendation table:

  • Severity — critical / high / medium / low / info
  • Category — Rightsizing, idle resources, reservation candidates, etc.

The filters compound — picking severity=high and a specific category narrows to recommendations matching both.

Recommendations Table​

Each row carries a severity badge, a category tag, an estimated monthly savings figure and a short description. The detail dialog (opened by clicking the row) renders the full recommendation payload — affected resource, recommended action, supporting metrics.

Cost Anomalies​

Incidents the platform classifies as cost-related (by source name, custom data or title heuristics) appear in a separate panel below the recommendations. Use this to investigate cost spikes that came in through the incident-ingest pipeline rather than being raised by the recommendation engine.

When the FinOps integration is configured the page exposes an Open in FinOps action that takes the user to the corresponding view in the standalone FinOps product. Use it when the team needs the deep cost-explorer UI for ad-hoc slicing.

Best Practices​

  • Filter to severity=critical or severity=high first — those are the recommendations that materially move the needle.
  • The Potential savings total is the aggregate if every recommendation were acted on; treat it as an upper bound, not a target.
  • Pair this page with Cloud for the underlying resource context — most rightsizing recommendations link directly to a cloud resource.
  • Configure the FinOps integration in Settings → FinOps before sharing this page with stakeholders.
  • Cloud — Cloud integrations whose resources the recommendations apply to
  • Incidents — Where cost-related anomalies live
  • Settings — FinOps integration configuration