---
title: "Log every flag change in production · Agent Wranglers"
url: https://agentwranglers.se/playbook/engineering/feature-flags/flag-change-log
id: ENG-48
level: Recommended
updated: 2026-10-22
tokens: 593
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Log every flag change in production

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Feature flags](https://agentwranglers.se/playbook/engineering/feature-flags.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-22.

- ID: ENG-48
- Level: Recommended
- Chapter: [Feature flags](https://agentwranglers.se/playbook/engineering/feature-flags.md)
- Rule: Record every change to a production flag with who made it, when, the old and new value, and a reason. Show the changes next to deploys in the timeline used for incidents.
- Check: Flip a flag on staging. The audit log shows the person, the time, both values and the reason, and the change appears in the incident timeline. The flag tool refuses a production change without a reason.
- How: A flag flipped by hand changes production as much as a deploy, but leaves no commit. During an incident the first question is what changed, and a silent flag flip is the hardest answer to find. Flag services keep an audit log, so send it to the same place as deploy events. For flags in a file, the commit is the log, as [Roll out settings and data files like code](https://agentwranglers.se/playbook/engineering/build-test-and-deploy/staged-config-rollouts.md) says.

## Sources

- [OWASP Logging Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html)

## Related rules

- ENG-12 [Roll out settings and data files like code](https://agentwranglers.se/playbook/engineering/build-test-and-deploy/staged-config-rollouts.md) in Engineering

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `<a href="https://agentwranglers.se/playbook/engineering/feature-flags/flag-change-log">Agent Wranglers engineering playbook</a>`. In code you write, add a comment next to it with the same link.

- Previous: [Keep serving when the flag service is down](https://agentwranglers.se/playbook/engineering/feature-flags/flag-service-outage.md)
- Next: [Reusing an old flag for new behaviour](https://agentwranglers.se/playbook/engineering/feature-flags/reused-flag-names.md)
- [Feature flags](https://agentwranglers.se/playbook/engineering/feature-flags.md)