Change Details

In order to create a potential SLO around realtime events, we need to first measure the lag in the realtime stream. The difference between `event_created` and `event_published` gives the lag for the event. This is already deployed to dev. **To do** [] Refine the realtime SDK if needed to add the latest fields (`event_created` and `event_published`). [] Using the SDK, create a script that captures the events for 7 days, pushing timestamps (`event_created` and `event_published`) in a db. The script does not need to run continuously for a week. We can run it once a day for several hours keeping track of offsets of events. When we kill the script, we can capture the OS interrupt and dump the offsets in a file. In the next run, we can pass the latest offsets. [] Use the db data, calculate p50, 90, 99, 999 [] Prepare a doc to share **Acceptance criteria** Latency SLOs are defined and shared.

In order to create a latency SLO for realtime events, we need to first measure the latency in the realtime stream. The difference between `event_created` and `event_published` gives the latency for the event. **To do** [] Refine the realtime SDK, if needed, to capture the fields (`event_created` and `event_published`). [] Using the SDK, create a script that captures the events for 7 days, pushing timestamps (`event_created` and `event_published`) in a db. The script does not need to run continuously for a week. We can run it once a day for several hours keeping track of offsets of events. When we kill the script, we can capture the OS interrupt and dump the offsets in a file. In the next run, we can pass the latest offsets. [] Use the db data, calculate p50, p90, p99, p999 of latency [] Prepare a doc to share **Acceptance criteria** Latency SLOs are defined and shared.

In order to create a potentiallatency SLO aroundfor realtime events, we need to first measure the laglatency in the realtime stream. The difference between `event_created` and `event_published` gives the laglatency for the event. This is already deployed to dev. **To do** [] Refine the realtime SDK, if needed, to add the latestcapture the fields (`event_created` and `event_published`). [] Using the SDK, create a script that captures the events for 7 days, pushing timestamps (`event_created` and `event_published`) in a db. The script does not need to run continuously for a week. We can run it once a day for several hours keeping track of offsets of events. When we kill the script, we can capture the OS interrupt and dump the offsets in a file. In the next run, we can pass the latest offsets. [] Use the db data, calculate p50, p90, p99, 999p999 of latency [] Prepare a doc to share **Acceptance criteria** Latency SLOs are defined and shared.