Fix or remove noisy ddtrace info log for after_in_child hook

[robrap]

Here is an example message:

2025-01-06 16:06:52,552 INFO 1 [request_id None] [ddtrace.internal.forksafe] forksafe.py:69 - after_in_child hook reset_at_fork was unregistered without first being registered

On 2024-01-06, I added a temp log retention filter of 99% exclusion for:

• "after_in_child hook reset_at_fork was unregistered without first being registered"

Note: Although we aren't indexing this, it will still appear in Live Tail view.

Acceptance Criteria

• Create or update DD support ticket to learn if DD will fix or if this should be ignored.
• Confirm fix (log messages no longer appearing), or bump filter to 100% and remove "[TEMP]" designation from name if we need to permanently ignore. (bumped to 100% on Feb 19)
• Remove "[TEMP]" log retention rule once DD removal of this log message has made it to Production. (see comments for details)

[jristau1984]

Arch-BOM (Tim) will inform DataDog about this, and support Aurora (Rodrigo) while that team looks into it for their specific service.

[robrap]

@timmc-edx: I unassigned you because you are no longer on-call. Either I will get to this as part of on-call, or anyone who frees up can get this. Also, I updated the AC to clarify that the only think we are doing for not is creating the DD support ticket.

[robrap]

The support ticket was created: https://help.datadoghq.com/hc/en-us/requests/1995270. I'm going to move this to the backlog, although I may follow-up on the DD Support ticket.

[robrap]

I added some comments to the DD ticket. I also rehydrated logs so I could discover when this problem first started. The problem started for us around 12pm on Oct 30, 2024.

[robrap]

[inform] We may need to see if this can be reproduced locally, and not sure if it requires gunicorn on devstack.

• See Devstack doesn't use gunicorn devstack#92 (comment)

[robrap]

From DD support ticket:

Additionally, a fix for this issue is included in the release candidate for 3.x and will be available when version 3.x is officially released. You can find more details here: Release 3.0.0rc2 · DataDog/dd-trace-py.

Once this lands, we should be able to remove the rule. We could change the rule to 0% first and ensure the messages don't reappear.

I don't know how long it will take to get to a 3.x release, so I'm going to have us look at this next quarter for a review date.

I also change this to P3, because I think clean-up is important.