Operations, debugging and cloud cost

How to find what changed when something breaks, how drift and upgrades are handled, and the restart, scaling, monitoring and cost tools Facets includes.

Facets records every change to every resource, so debugging starts from what changed.

When something breaks

Start from what changed: each resource's Release History lists every change, with who made it and when.

For a failed release, AI debugging or Praxis reports the likely cause and fix.

Drift: changes made outside Facets

Facets doesn't watch for drift all the time. A release with Refresh finds it, and applying that release puts the resources back to match the blueprint.

Upgrades without downtime

Upgrades run when you choose: in a maintenance window you set, or as a release you start.

In Facets' catalog modules, the Kubernetes version is a cluster setting, GKE and AKS node pools start new nodes before removing old ones, and whether a database restarts depends on the cloud's database service.

Restart and scale

Each resource has actions, such as restart, scale and Helm rollback, and your platform team can add its own, such as a database snapshot.

Monitoring, cost and alerts

Each environment runs Prometheus, Grafana and Alertmanager.

Alerts, chat and other tools

Facets sends alerts and release updates to Slack, Microsoft Teams, PagerDuty, Zenduty or any webhook.