fly-log-shipper application suspends automatically

1

Hi there,

I successfully deployed the superfly/fly-log-shipper image a few days ago. The fly.toml configuration is:

app = 'lynden-logshipper'
primary_region = 'arn'

[build]
  image = 'ghcr.io/superfly/fly-log-shipper:latest'

[http_service]
  internal_port = 8080
  force_https = true
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 0
  processes = ['app']

[[vm]]
  memory = '1gb'
  cpu_kind = 'shared'
  cpus = 1

[[services]]
  http_checks = []
  internal_port = 8686

[env]
  SUBJECT = 'logs.trader-realtime.>'

I have added it as a source to Better Stack with the correct environment variables set.

The set-up works fine for some time (I can’t say for sure how long, but suspect hours - the logs are empty by now). But then Fly.IO reports that the logshipper application has been suspended. Its status is indeed “stopped”. What might cause this behaviour, and how could I fix it?

Thank you,
Martin

2

Actually, the problem is staring me right in the face. I have auto_stop_machines set to true… My bad…

3

I run my log aggregator without exposing it to public, since there’s no need to. But I guess that depends on your usecase.

If you want to store and run your own logs, you can get my source code here. Here’s a video of how it works https://youtu.be/sQT9fQsuNUs?si=KpzMO4tyqG6lXTlY

4

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