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** [] Either subscribe to dev realtime or use ksqldb dev instance. Capture `event_published` and `event_created` over 2-3 days. [] Get these statistics: - Average lag - Max lag - What percentage of events have a lag smaller than 500 ms - What percentage of events have a lag smaller than 1 s - What percentage of events have a lag smaller than 2 s - What percentage of events have a lag smaller than 3 s - What percentage of events have a lag smaller than 5 s - What percentage of events have a lag smaller than 10 s - What percentage of events have a lag smaller than 30 s - What percentage of events have a lag smaller than 1 m - What percentage of events have a lag smaller than 2 m - What percentage of events have a lag smaller than 5 m

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** [] Either subscribe to dev realtime or use ksqldb dev instance. Capture `event_published` and `event_created` over 2-3 days. [] Get these statistics: - Average lag - Max lag - What percentage of events have a lag smaller than 500 ms - What percentage of events have a lag smaller than 1 s - What percentage of events have a lag smaller than 2 s - What percentage of events have a lag smaller than 3 s - What percentage of events have a lag smaller than 5 s - What percentage of events have a lag smaller than 10 s - What percentage of events have a lag smaller than 30 s - What percentage of events have a lag smaller than 1 m - What percentage of events have a lag smaller than 2 m - What percentage of events have a lag smaller than 5 m

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** [] Either subscribe to dev realtime or use ksqldb dev instance. Capture `event_published` and `event_created` over 2-3 days. [] Get these statistics: - Average lag - Max lag - What percentage of events have a lag smaller than 500 ms - What percentage of events have a lag smaller than 1 s - What percentage of events have a lag smaller than 2 s - What percentage of events have a lag smaller than 3 s - What percentage of events have a lag smaller than 5 s - What percentage of events have a lag smaller than 10 s - What percentage of events have a lag smaller than 30 s - What percentage of events have a lag smaller than 1 m - What percentage of events have a lag smaller than 2 m - What percentage of events have a lag smaller than 5 m