Set up JavaScript error monitoring for my site

Sets up JavaScript error monitoring for a site you run, covering what to capture, alert rules, privacy and a weekly review.

Task: Set up JavaScript error monitoring for my site, from choosing what to capture to a weekly review habit. Context: My site is [site type] built with [framework] and gets about [visits per month] visits a month. I have [budget] a month, and a team of [team size] who can look at errors. Rules: - Say what an error report should contain to be useful, such as message, stack trace, page, browser and release, and what it must leave out, such as form values, tokens and personal data. - Cover grouping of duplicate errors, source maps, alert rules that avoid noise, and who gets which alert. - Tell me to choose between a hosted monitoring service and a self-hosted one by the questions I should ask, not by naming a winner. - Include a privacy step, such as telling users what is collected, and say to check my local rules with a qualified professional. Result: A numbered setup plan of at most 7 steps, a table of 4 alert rules (condition, who is told, how fast), and one sentence on the first thing to look at each week.

Updated