Objective

Ensure observability of the new website version: understand whether it is available, where errors occur, and whether key user scenarios are functioning.

What to do

• Define a minimum set of technical and user events to track.
• Restore or reconnect web analytics in the new implementation.
• Set up basic availability monitoring for public pages.
• Ensure logging of critical application errors and failed user actions.
• Verify that main forms and transitions can be diagnosed after launch.
• Make sure data collection does not break the user interface or create excessive requests.
• Prepare a simple set of checks to use in the first few days after switching over.

Result

The new version of the website has basic observability, and critical issues can be detected without manually browsing the entire site.

Definition of Done

• Basic analytics loads and records key events.
• Website availability can be monitored automatically or through regular checks.
• Critical errors do not remain completely invisible.
• There is a clear way to test forms and main user scenarios after launch.

Limitations

Do not publish tracker IDs, tokens, keys, internal monitoring system addresses, or other sensitive parameters.