rollfuse Solutions: Integration Use Cases and Guardrails

Automatic Deployment Rollback with Prometheus Metrics

A Prometheus query result reaches rollfuse as observations, and a guardrail aborts the rollout when the average over its window crosses the threshold.

Automatic Rollback From a Metric Your Grafana Already Reads

A connector reads a PromQL query through Grafana's data source proxy, and a guardrail aborts the rollout when the window's average crosses the threshold.

Correlate Flag Evaluations with OpenTelemetry Traces

Your service writes each evaluation's flag, variation and reason onto the active OpenTelemetry span, so a failing trace shows which variation served the request.

Automatic Feature Flag Rollback Driven by Datadog Metrics

A small job of yours reads a metric from Datadog and sends it to rollfuse, where a guardrail averages it over a window and aborts the rollout when it crosses your threshold.

Automatic Feature Flag Rollback Driven by New Relic Metrics

A small job of yours runs your NRQL query in New Relic and sends the result to rollfuse, where a guardrail averages it over a window and aborts the rollout when it crosses your threshold.

Feature Flags in Kubernetes Pods, Scoped by Environment

Each Kubernetes deployment carries the credential of one rollfuse environment, so its pods evaluate that environment's flags locally and follow rollout changes without a restart.

Gate a GitHub Actions Deploy Step on a rollfuse Flag

A single step in a GitHub Actions workflow evaluates a rollfuse flag and fails the job when it doesn't match the expected variation, blocking whatever runs after it.