Do `flyctl` metrics pose any privacy concerns?

I’ve got an interesting message today.

Warning: Metrics send issue: failed to send metrics: Post "https://flyctl-metrics.fly.dev/metrics_post": read tcp 192.168.100.27:57826->82.209.230.73:443: read: connection reset by peer

The message is caused by upstream firewall, but I wonder which metric does flyctl collect. I haven’t found it’s documented anywhere.

We don’t have a definitive list anywhere, though flyctl is open-source so one can spelunk there for what is being sent.

In general, we keep an eye on success/failure and timings for operations like fly launch and fly deploy, and general metrics like the version of flyctl being used.

You can also run fly settings analytics disable to fully opt-out of these metrics :slight_smile:

2 Likes

That’s useful. Thanks!

Although I am still curious what data shows about my system. :innocent:

it doesn’t report data about your system - it only reports data about your usage of flyctl (what version you’re running, how long some commands/steps take to run, …)

I am looking at this part.

If it reports processes running on my machine, it is bad.

those are not metrics collected from your machine, it’s fly.toml configuration for your app. see https://fly.io/docs/reference/configuration/#the-metrics-section

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.