Closed Bug 1868721 Opened 2 years ago Closed 2 years ago

RtpLogging produces inconsistent log format

Categories

(Core :: WebRTC, defect, P2)

defect

Tracking

()

RESOLVED FIXED
122 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox120 --- wontfix
firefox121 --- wontfix
firefox122 --- fixed

People

(Reporter: ng, Assigned: ng)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

The formatting of RtpLogger messages is largely up to the logging caller. The importance of this is not obvious, and has proven fragile. Adding a marker which indicates the portion of the message of interest would go a long way to making RtpLogger log messages easy to reformat for text2pcap ingestion.

The previous (broken) method of getting to portion of interest was:

cat log | egrep '(RTP_PACKET|RTCP_PACKET)' | cut -d '|' -f 2 | cut -d ' ' -f 5-

With this patch it is the following:

cat log  | rg 'RtpLogger.*RTC?P_PACKET|>>\s(?P<packet>.+$)' --only-matching  --replace '$packet'

The advantages are that none of key tokens in the new format come from the log site and the regex is more resilient to log message changes which would throw off cut operations.

Set release status flags based on info from the regressing bug 1848749

Severity: N/A → S3
Pushed by na-g@nostrum.com: https://hg.mozilla.org/integration/autoland/rev/b9b512531e17 make RtpLogger output format more robust;r=webrtc-reviewers,mjf
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: