Monthly channel ran extremely quickly (100ms). Hourly channel took the normal amount of time after that. Channel timestamp log, as depicted in the graph, only shows the monthly channel, and it shows it as taking the amount of time that both channels combined took. This doesn't happen for any of the other non-hourly channels.
The hourly channel timestamps were not recorded - they're not in the logged outbound S3 storage request, and they're not in the inbound CloudFront json response - only the monthly. The frontend naively interprets the gap between monthy and the start of cleanup as belonging to the monthly channel.
Might be worth checking if the hourly channel was recorded to the database. I should also start logging timestamp record events so I don't have to do that in future.
Impact: almost none, slight inaccuracy in graph.
Monthly channel ran extremely quickly (100ms). Hourly channel took the normal amount of time after that. Channel timestamp log, as depicted in the graph, only shows the monthly channel, and it shows it as taking the amount of time that both channels combined took. This doesn't happen for any of the other non-hourly channels.
The hourly channel timestamps were not recorded - they're not in the logged outbound S3 storage request, and they're not in the inbound CloudFront json response - only the monthly. The frontend naively interprets the gap between monthy and the start of cleanup as belonging to the monthly channel.
Might be worth checking if the hourly channel was recorded to the database. I should also start logging timestamp record events so I don't have to do that in future.
Impact: almost none, slight inaccuracy in graph.