LaunchDarkly change history, beside the metric the flag moved.
LaunchDarkly logs every flag change — but it’s buried in the dashboard, flag by flag, where only engineers ever look. CoNote will put each toggle and rollout change on one shared timeline, beside the deploys and incidents from the same day.
Flag “new-checkout” turned on for 100% of users
LaunchDarkly· 11:20
Checkout error rate spiked
Uptime· 11:24
Finding your history
Your LaunchDarkly change history: today, and once CoNote is live
The manual way · inside LaunchDarkly
Where to find it today
It’s all there — if you go digging:
- 1
Sign in to LaunchDarkly
Open the project and environment you need — flags and their history are scoped per environment, so production is separate from staging.
- 2
Open a flag’s history
Each flag has a history (or change log) showing every change to it — who toggled it, the rollout percentage, and when.
- 3
Check the audit log
The account-level audit log lists changes across flags, which you can filter by date, member, and resource.
- 4
Open a change for the detail
Click an entry to see exactly what changed — the targeting rule, the percentage rollout, or the on/off switch.
- 5
Cross-reference the dates by hand
Nothing lines flag changes up against your deploys or analytics, so you reconstruct that yourself when a metric moves.
The CoNote way · coming soon
Where you’ll find it once it’s live
Connect LaunchDarkly once. After that it’ll be seconds:
- 1
Open your CoNote timeline
Every flag change will be waiting — no dashboard access, no flag-by-flag digging, readable by anyone.
- 2
Jump to the day it moved
Scan the day the metric shifted; the toggle or rollout change will be stamped there to the minute.
- 3
See it beside everything else
The flag change will sit next to that day’s deploys and incidents — the cause is obvious.
Sound familiar?
A flag change moves things — with no deploy to blame.
Nadja11:25
Tom11:29
Sara11:32
Tom11:37
A change with no deploy — the hardest kind to find.
LaunchDarkly logs every toggle, but flag by flag, in the dashboard — never lined up against the metric it moved, so a change with no deploy is the hardest kind to trace.
- Flag by flag — no single feed of every change
- Per environment — production history separate from the rest
- Locked in the dashboard, where the rest of the team never looks
- Never lined up against the deploy, incident, or metric from the same day
Once LaunchDarkly is connected, the change will already be on the timeline — “Flag ‘new-checkout’ turned on for 100% of users” — stamped to the minute, next to the deploy and the metric it moved.
How it works
Connect once. Then it’ll log itself.
- 01
Connect LaunchDarkly
A one-time connection — no SDK changes, no engineering sprint. CoNote will receive the flag changes you choose to track.
- 02
Every flag change logs itself
From then on, each toggle and rollout change lands on the timeline with what changed and who changed it — “Flag ‘new-checkout’ turned on for 100% of users”.
- 03
Read it in context
The flag change sits beside that day’s deploys and incidents. When a metric moves with no deploy, the flag is right there.
What lands on your timeline
- Flag toggles — turned on, off, and by whom
- Rollout changes — the new percentage or targeting
- The moment each change went live, to the minute
In your week
What teams will use it for.
The incident with no deploy
Errors spike but nothing shipped. The flag rolled to 100% at 11:20 is right there on the timeline — the change you’d otherwise hunt for flag by flag.
Credit the rollout, not a phantom deploy
Conversion jumps with no release. The flag rollout is dated next to the day it moved, so you credit the right change.
Who flipped this flag?
Every toggle is logged with who made it and when — so the answer is on the timeline, not in a Slack thread.
Flags and deploys on one timeline
Code changes and flag changes — the two ways your product shifts — finally sit side by side, in order.
Side by side
Native history vs. your logbook.
See flag toggles and rollouts
LaunchDarkly history
CoNote
One feed across every flag
LaunchDarkly history
CoNote
Lined up against deploys and incidents
LaunchDarkly history
CoNote
Readable by the whole team
LaunchDarkly history
CoNote
Surfaces changes with no deploy
LaunchDarkly history
CoNote
Setup
LaunchDarkly history
CoNote
On the timeline
The change in context.
A flag toggle on its own is a dashboard row. Next to the error spike from the same minute, it’s the answer to “nothing deployed, so what happened?”
Tuesday, June 9
Flag “new-checkout” turned on for 100% of users
LaunchDarkly· 11:20
Checkout error rate spiked
Uptime· 11:24
Deployed storefront v2.4.0 (main → 3a7f2c1)
GitHub· 09:41
Questions
LaunchDarkly change tracking, answered.
Each flag has its own history showing every change — who toggled it, the rollout percentage, and when. The account-level audit log lists changes across flags, filterable by date, member, and resource. History is scoped per environment.
Not yet — it’s coming soon. You can start your CoNote logbook now and connect the tools that are already live; we’ll switch LaunchDarkly on automatically the day it ships.
No. Connecting LaunchDarkly will be a one-time connection in CoNote — no SDK changes and no changes to how your flags work.
It logs the flag toggles and rollout changes you choose to track — typically your production flags — so the timeline stays meaningful rather than noisy.
Flag toggles, rollout percentage changes, and targeting changes — each as a plain-language entry with who made it and the time it went live.
LaunchDarkly’s history is flag by flag, per environment, in the dashboard, where only engineers look. CoNote will put those changes on one shared timeline next to deploys and incidents — so a change with no deploy is finally easy to spot.
Only your team. Every entry is scoped to your team, and connecting LaunchDarkly won’t expose your flags to anyone outside it.
Keep digging
Track the rest of your stack.
Open the logbook.
Free plan, no card. The next time someone asks “what changed?”, the answer is one search away.
Start your logbook