🌸 Cherry-pick request for #32892 into #32874 (Pending)

[samouri]

Cherry-pick request

Issue	PR	Beta / Experimental?	Stable?	LTS?	Release issue
ampproject/error-reporting#54	#32892	YES	NO	NO	#32874

Why does this issue meet the cherry-pick criteria?

• The issue creates a ton of noise in our error logs. Many many many spurious error reports per day. It is not user observable (unless they check network logs) and therefore not P0, so we should not attempt to patch stable. I believe it is still worth CPing the revert to Beta, in which it should have a few days to bake before being promoted to stable.
• The diff is a revert and innocuous.

note: I am unsure if this is truly CP worthy, and am interested in second opinions! To see the impact, check the error dashboard which contains multiple separate errors with the same name "attempting to trigger analytics for detached target"

List the steps to manually verify the changes in this cherry-pick

• I don't know how to reproduce. No verification needed beyond seeing the report remove from logs.

Mini-postmortem

TODO: This postmortem will be written after the cherry-pick deployment and before this issue is closed. Delete this TODO when the postmortem is ready.

Summary

<1-2 sentences summarizing the problem and root causes.>

Impact

• <Which users were affected? Roughly how many?>
• <How were users affected? E.g. partial or complete loss of functionality?>

Action Items

• #<ISSUE_NUMBER>: <Add unit/integration/end-to-end test>
• #<ISSUE_NUMBER>: <Add monitoring for edge case via error logging>
• #<ISSUE_NUMBER>: <Refactor an easily misused API>

---

/cc @ampproject/release-on-duty @ampproject/wg-approvers @ampproject/cherry-pick-approvers

[kristoferbaxter]

Since we already have several high priority cherrypicks happening right now, let's defer this logging output change to the next stable release.

[samouri]

It should be in the new Beta cut this week, so lets just close this and let it be fixed according to usual release schedule