Fly Logshipper × Better Stack LogTail

I followed Fly’s guide for configuring a log shipper, and we’re seeing some weird sink errors here. All the secrets were created, again following the documentation provided, like the access token, Better Stack source token, and ingestion source.

Has anyone encountered this?

ERROR sink{component_kind=“sink” component_id=better_stack component_type=http component_name=better_stack}:request{request_id=0}: vector_common::internal_event::component_events_dropped: Events dropped intentional=false count=1 reason=“Service call failed. No retries or retries exhausted.” internal_log_rate_limit=true

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