Datadog, Oodle & live guardrail checks
Connect Datadog or Oodle with an API key and use those streams as guardrail signals, pick metrics from a live catalog instead of typing names from memory, and pull a reading on demand with Check now — including a reason when a signal cannot be read.
Datadog & Oodle connectors
Datadog and Oodle join the integration catalog. Connect with an API key — no OAuth dance — and use your logs, metrics, traces, errors, and latency as stability signals for guardrails, alongside OpenObserve and the providers you already use.
Pick metrics from the catalog
The guardrail editor now lists metrics your provider actually emits. Pick a name from the catalog instead of hoping the string you remembered is the one the soak will query.
Check now
Need a number that is not the last soak decision? Check now pulls a live reading against your own provider, on demand. A human hold stops observation and says so; if a signal cannot be read, the console names the reason instead of looking like a healthy zero.
Improved
- Automatic vs manual is per-rollout, with reasons when auto is blocked
- Guardrail metrics stay editable after the seal — the ramp picks up the new list
- Pause keeps an automatic ramp on Auto (Paused); Ramp up / Ramp down step then re-pause
- fw self-update crosses stable and staging even when the version number matches
- The CLI installer persists fw on your PATH across shells
- Initialise issues project keys in the console — it no longer writes credentials to disk
Fixed
- A healthy metric no longer rolls the release back
- A connect-time probe can read the credential you just pasted
- The ramp no longer watches an empty metric list on every rollout