[tcbyrd]

Something I’ve been thinking about lately around all these external observability tools. Does streaming logs count towards your outbound bandwidth from providers like Vercel/Netlify/etc? One huge benefit to using everything the cloud provider gives you is all of it stays “on-net”, so to speak. I wonder if I use a tool like this or Honeycomb, am I not only monitoring ingest costs but also egress from the app provider. A lot of these solutions are hosted on top of AWS, so it would be awesome to find out they zero-rate traffic between them, but I feel like that’s probably not the case?

[njpatel]

In the case of Axiom & Vercel, you'll only be paying for ingest (if you need over 2GB/day) and no bandwidth costs. I believe the latter is the case with all of Vercel's observability partners (and with most services providing a log-drains service).

It's a fair point, though...at some point, and with enough TBs of traffic, it could get expensive to provide the log drain support. One thing we've been working on (and more on this in the coming weeks), is putting together a benchmark of log-drain mechanisms to try and work out what would be the most efficient combo of compression/cpu/mem to use for log-drain providers.

Our hope is we can work on making it efficient enough that we can encourage more services to provide log-drains (and therefore allow us to make great experiences around those logs!).

[lizthegrey]

Ask your observability provider about PrivateLink, or talk to your account rep at AWS about discounting traffic.

But also, you can sample some of the data within your own VPCs (see Honeycomb's Refinery or Lightstep's Satellites)