Issue (include links if applicable):
Logstash dashboard shows a high amount of EventGate validation errors for CX events: https://logstash.wikimedia.org/goto/2234659c7b149ebfc3c1d4695568e602
The error is '.translation_source_title' should be string
~3.5K events were affected by this error during the past 90 days.
What should have happened instead?:
There can be two scenarios why this might be happening (both should be checked for)
- Events for which these events are not relevant, for example, tab selection, and explicitly being set to null. For events which fields which are not relevant, they should not be set to null. Missing fields will be set to null during ingestion. Please see: Event_Platform/Schemas/Guidelines#Optional_/_Missing_fields
- Events for which these fields are applicable, but are null for some reason. For example, there are several editor_open events which have this errors as well. At the time of editor being opened, user would have already selected the source, so I'd expect a value for these events.
Also note: the spike errors seems to have started during mid March, coinciding with the unified CX dashboard release to desktop.
Test Case 1: Verify events with null or empty .translation_source_title
- Trigger a CX event for which .translation_source_title is not relevant or is null (e.g., tab selection).
- Capture the event payload sent to EventGate.
- ✅❌❓⬜ AC1: Confirm that .translation_source_title is removed entirely from the payload.
QA Results - Logstash
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T395417#11372839 |
