Backend: Error Monitoring
Go
JS
Python
Ruby
Backend: Logging
Fullstack Frameworks
Self Host & Local Dev
Menu
Fly.io NATS Log Shipper
Learn how to setup Highlight log ingestion on [Fly.io](https://fly.io/blog/shipping-logs/). As a prerequisite, we assume you already have an application deployed on Fly.io and `flyctl` configured locally.
1
Spin up the highlight.io logs shipper alongside your fly.io deployment.
Clone our sample fly-logs-shipper fork that configures the highlight-io vector logs drain. Launching an empty app first is a workaround until our logs shipper is merged with the main one.
git clone git@github.com:highlight/fly-log-shipper.git
cd fly-log-shippermv fly.toml fly.toml.tempfly launchmv fly.toml.temp fly.toml2
Configure and launch the logs shipper.
No other work is needed on the side of your application, as fly apps are already sending monitoring information back to fly which we can read. Check out the README.md for more details.
# set the org for your deployment
fly secrets set ORG=personal# give the logs shipper access to other containers' logs
fly secrets set ACCESS_TOKEN=$(fly auth token)# set to configure your highlight project
fly secrets set HIGHLIGHT_PROJECT_ID=<YOUR_PROJECT_ID>fly launch3
Verify your backend logs are being recorded.
Visit the highlight logs portal and check that backend logs are coming in.