fly-log-shipper error on launch/deploy - nats: Authorization Violation

Questions / Help
1

I am attempting to integrate GitHub - superfly/fly-log-shipper: Ship logs from fly to other providers with Datadog. Following the setup instructions, i set the following specified secret:

fly secrets set DATADOG_API_KEY=xxxxx

The deploy fails, and logs show

2022-07-25T14:53:50Z app[5e98d772] sea [info]nats: Authorization Violation
2022-07-25T14:53:50Z app[5e98d772] sea [info]2022-07-25T14:53:50.137179Z  INFO source{component_kind="source" component_id=fly_socket component_type=socket component_name=fly_socket}:connection: vector::sources::util::unix_stream: Finished sending.
2022-07-25T14:53:50Z app[5e98d772] sea [info]2022-07-25T14:53:50.138091Z  INFO vector: Vector has stopped.
2022-07-25T14:53:50Z app[5e98d772] sea [info]2022-07-25T14:53:50.139373Z  INFO vector::topology::running: Shutting down... Waiting on running components. remaining_components="fly_log_metrics_prometheus, fly_log_metrics, datadog, blackhole" time_remaining="59 seconds left"
2022-07-25T14:53:50Z app[5e98d772] sea [info]2022-07-25T14:53:50.139572Z  INFO vector::sinks::blackhole::sink: Total events collected events=0 raw_bytes_collected=0
2022-07-25T14:53:50Z app[5e98d772] sea [info]2022-07-25T14:53:50.261411Z  INFO vector::topology::builder: Healthcheck: Passed.
2022-07-25T14:53:50Z app[5e98d772] sea [info]Main child exited normally with code: 0
2022-07-25T14:53:50Z app[5e98d772] sea [info]Starting clean up.

To be sure there wasn’t an issue with the token i used, i created a new one in Datadog and again did

fly secrets set DATADOG_API_KEY=xxxxx

The subsequent deploy threw the same error.

2

Have you also set the required Fly secrets for ORG and ACCESS_TOKEN (GitHub - superfly/fly-log-shipper: Ship logs from fly to other providers)? It sounds like the log shipper isn’t authenticating correctly to the nats log source.