Change Details

As a part of our latency SLO work for realtime feed, we need to log events that are exceeding p999 latency. This will allow us to monitor and create alert in future. **To do** [x] Add an env variable to structured-data : `LatencyThreshold` [x] In structured-data handlers, before events are published to the topics, check `event_published` - `event_created`. If this is > p999, log it along with `event.identifier` **QA (Acceptance criteria)** Able to see few logs in cloudwatch of the above type.

> OKR O6.KR1 As a part of our latency SLO work for realtime feed, we need to log events that are exceeding p999 latency. This will allow us to monitor and create alert in future. **To do** [x] Add an env variable to structured-data : `LatencyThreshold` [x] In structured-data handlers, before events are published to the topics, check `event_published` - `event_created`. If this is > p999, log it along with `event.identifier` **QA (Acceptance criteria)** Able to see few logs in cloudwatch of the above type.

> OKR O6.KR1 As a part of our latency SLO work for realtime feed, we need to log events that are exceeding p999 latency. This will allow us to monitor and create alert in future. **To do** [x] Add an env variable to structured-data : `LatencyThreshold` [x] In structured-data handlers, before events are published to the topics, check `event_published` - `event_created`. If this is > p999, log it along with `event.identifier` **QA (Acceptance criteria)** Able to see few logs in cloudwatch of the above type.