FIDES-1977: Overhaul fides-privacy-center logging (JSON logging, configurable log levels) and add option to throw error when server-side experience lookup fails

[tvandort]

Closes FIDES-1977

Description Of Changes

Allow different empty experience fallback mechanisms.
Improve logging in Privacy Center.

Steps to Confirm

1. Use cookiehouse while the Fides API isn't running with the following set:

FIDES_PRIVACY_CENTER__MISSING_EXPERIENCE_BEHAVIOR=throw
FIDES_PRIVACY_CENTER__LOG_LEVEL=debug

Observe that the PC 500s and logs per retry are listed.

2. Use cookiehouse with the Fides API running with the following set:

FIDES_PRIVACY_CENTER__MISSING_EXPERIENCE_BEHAVIOR=throw

Observe that everything works as it used to but

3. Use cookiehouse with Fides API running with the following set:

FIDES_PRIVACY_CENTER__MISSING_EXPERIENCE_BEHAVIOR=empty_experience

Observe that an empty experience is returned.

4. Use cookiehouse while Fides API is not running with the following set:

FIDES_PRIVACY_CENTER__MISSING_EXPERIENCE_BEHAVIOR=empty_experience

Observe that an empty experience is returned.

5. Adjust the log level to info and observe that there are no debug logs.

6. Observe that each log made during a HTTP request logs a request ID that is the same across messages.

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fides-privacy-center	❌ Failed (Inspect)			May 21, 2025 7:22pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	⬜️ Ignored (Inspect)	Visit Preview		May 21, 2025 7:22pm

[lucanovera]

Good work! I left 1 suggestions for simplifying the code and a recommendation for using a library to handle the retry functionality.

[NevilleS]

Ugh, I apologize for this "request changes", knowing that we're piling QoL asks onto a request that was originally fairly simple 👍

[NevilleS]

This is great - we have some issues with the fides-privacy-center Vercel deployment, but that's almost certainly a red herring.

[cypress]

fides    Run #12938

Run Properties:   Passed #12938  •  7b61d77cb0: FIDES-1977: Overhaul fides-privacy-center logging (JSON logging, configurable lo...

Project	fides
Branch Review	main
Run status	Passed #12938
Run duration	00m 50s
Commit	7b61d77cb0: FIDES-1977: Overhaul fides-privacy-center logging (JSON logging, configurable lo...
Committer	Tom Van Dort
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	0
Skipped	0
Passing	5
View all changes introduced in this branch ↗︎