Integrations
Turn feedback about a feature rollout into Jev labels and durable Prometheus counters that an Unleash rollout policy can monitor.
Only you can see your notes.
Screenshot unavailable. Open the experiment ↗
Feedback is tied to a named flag and environment, with event IDs used to avoid counting retries twice. Jev does not disable features itself: configured Unleash rules decide what happens. The documented release-management path requires Unleash Enterprise; no live Unleash integration was verified.
If your team releases features gradually with Unleash, ask a developer to study these feedback examples. Jev judges whether comments describe something that stopped working after a change. A monitoring tool reads the counts. Your team chooses what happens next; Jev does not disable a feature.
Feedback text leaves your system for Jev to judge. If you change the questions or answer choices, counting starts again. Repeated events must not be counted twice. This example needs Unleash’s Enterprise edition. A label does not prove what caused a failure.