Log Shipper Shipping Mystery Bytes

I run a dinky little web app (loaded for a few minutes per week by ~60 people) from my personal org, so was surprised this month to be billed for 717GB of outbound data transfer. Hah!

I was further surprised to find that my instance of fly-log-shipper was the responsible party. Over the last ~7 months that it’s been active, it appears to have only shipped about 10mb worth of logs to my configured S3 bucket, but over the last month appears to have been doing something expensive, averaging about 312kb/s of outbound transfer.

Screen Shot 2023-01-02 at 10.21.36 PM

Simply re-deploying it seemed to have knocked that down to something more reasonable (~4kb/s), but I’m wondering if anybody more familiar with vector or the internals of how its deployed within fly.io might be able to explain what the heck happened, and if there’s something I should be doing to prevent it going haywire again.

$15 of outbound data isn’t the end of the world by any means, but just seems to have been doing something very unexpected.