Fly.io
To integrate with Fly.io, you'll need to stand up HyperDX's Fly log shipper, which extends the functionality of the default Fly log shipper.
This Guide Integrates:
✅ Logs | ✖️ Metrics | ✖️ Traces |
To send over metrics or APM/traces, you'll need to add the corresponding language integration to your application as well.
Note: It's currently not possible to ship logs to HyperDX using the standard log shipper.
# Make a directory for your log shipper app
mkdir hyperdxlogshippper
cd hyperdxlogshippper
# Create the app but don't deploy just yet
fly launch --no-deploy --image ghcr.io/hyperdxio/fly-log-shipper:latest
# Set required secrets, including your HyperDX API key
fly secrets set ORG=personal
fly secrets set ACCESS_TOKEN=$(fly auth token)
fly secrets set HYPERDX_API_KEY="<YOUR_API_KEY_HERE>"
Before deploying the log shipper, you'll need to edit the generated fly.toml
and replace the entire [[services]]
section with:
[[services]]
http_checks = []
internal_port = 8686
To ensure the log shipper will pass health checks.
Then you can deploy the log shipper:
fly deploy --ha=false
We'll need to disable high availability for the log shipper deployment, as we only want a single instance (to prevent duplicate logs from being sent). For an HA setup, you can follow the instrucitons here (opens in a new tab).
Read more about Fly's log shipper here (opens in a new tab).