fix(replays): add more robust as_log_message tests

[michellewzhang]

🚨 for actual test changes: use this view https://github.com/getsentry/sentry/pull/98482/files/9500752d1c341f3a051599c7e5bd40deb8143f18

closes https://linear.app/getsentry/issue/REPLAY-621/create-log-parsing-test-suite-with-real-replay-event-data

• use real replay events to test as_log_message. serves as an example for reliable test data that can be referenced in the future. all types in EventType are tested
• validates that get_timestamp_unit returns the correct timestamp based on the real replay data
• fixed a bug where feedback breadcrumbs were incorrectly categorized as s when they should be ms
• validates that the log message timestamp is always in MS

sentry/src/sentry/replays/usecases/ingest/event_parser.py

Lines 220 to 256 in 950bfbe

	def get_timestamp_unit(event_type: EventType) -> Literal["s", "ms"]:
	"""
	Returns the time unit of event["timestamp"] for a replay event.
	This is not guaranteed to match event.data.payload.timestamp.
	We do not allow wildcard or default cases. Please be explicit when adding new types.
	Beware that EventType.UNKNOWN returns "ms" but there's no way to know the actual unit.
	"""
	match event_type:
	case (
	EventType.CLS
	| EventType.LCP
	| EventType.FEEDBACK
	| EventType.MEMORY
	| EventType.MUTATIONS
	| EventType.NAVIGATION_SPAN
	| EventType.RESOURCE_FETCH
	| EventType.RESOURCE_IMAGE
	| EventType.RESOURCE_SCRIPT
	| EventType.RESOURCE_XHR
	| EventType.UI_BLUR
	| EventType.UI_FOCUS
	):
	return "s"
	case (
	EventType.CANVAS
	| EventType.CONSOLE
	| EventType.CLICK
	| EventType.DEAD_CLICK
	| EventType.RAGE_CLICK
	| EventType.SLOW_CLICK
	| EventType.HYDRATION_ERROR
	| EventType.NAVIGATION
	| EventType.OPTIONS
	| EventType.UNKNOWN
	):
	return "ms"

[linear]

REPLAY-621 Create log parsing test suite with real replay event data

[cmanallen]

This file should be a use case: src/sentry/replays/lib/summarize.py.

A library should be generic and totally unrelated to replay. This is coupled to replay so its an implementation detail of the product. You don't have to address on this PR. But eventually it should be moved.

[michellewzhang]

This file should be a use case: src/sentry/replays/lib/summarize.py.

A library should be generic and totally unrelated to replay. This is coupled to replay so its an implementation detail of the product. You don't have to address on this PR. But eventually it should be moved.

@cmanallen moved! (both that file & the test file)

[cmanallen]

thank you!