"failed to find message" warning when viewing logs without a body in transactions screen

[codefromthecrypt]

Kibana version: 8.16.0

Elasticsearch version: 8.16.0

Server OS version: Darwin 24.1.0

Browser version: Chrome 130.0.6723.117

Browser OS version: Darwin 24.1.0

Original install method (e.g. download page, yum, from source, etc.): docker

Describe the bug: If you use the transactions view, the log event without a message results in "failed to find message", though it is fine in the logs explorer

Steps to reproduce:

example log event from otel

{
    "body": null,
    "severity_number": "<SeverityNumber.INFO: 9>",
    "severity_text": null,
    "attributes": {
        "gen_ai.system": "openai",
        "event.name": "gen_ai.user.message"
    },
    "dropped_attributes": 0,
    "timestamp": "2024-11-19T04:25:14.265495Z",
    "observed_timestamp": "2024-11-19T04:25:14.265502Z",
    "trace_id": "0x36bcd3fe31ecb235cd6c3786c9fe4eec",
    "span_id": "0xe2eab7207ab51f90",
    "trace_flags": 1,
    "resource": {
        "attributes": {
            "telemetry.sdk.language": "python",
            "telemetry.sdk.name": "opentelemetry",
            "telemetry.sdk.version": "1.28.2",
            "service.name": "opentelemetry-python-openai",
            "telemetry.auto.version": "0.49b2"
        },
        "schema_url": ""
    }
}

Expected behavior:

a different behavior, perhaps listing tag/attributes as done in the logs explorer, or in worst case no message or "n/a"

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

[elasticmachine]

Pinging @elastic/unified-observability (Team:Observability)

[weltenwort]

💭 This would be fixed once we replace the shared logs stream component with the saved search component.