Fly Log Shipper not picking up logs

Questions / Help
1

Hi All,

I’m testing out the Fly Log Shipper to ship my logs to a provider using a custom http sink. So, I’m building a Dockerfile based off of the log-shipper image and copying my custom http sink to the sinks directory. The logs in the log-shipper app just show:

2023-10-13T15:57:02.257 app[4d8913e7b2d438] sea [info] 2023-10-13T15:57:02.257549Z INFO vector::internal_events::api: API server running. address=0.0.0.0:8686 playground=http://0.0.0.0:8686/playground

And no logs arrive at my provider. Here is the custom http sink and Dockerfile:

[sinks.http]
  type = "http"
  inputs = ["log_json"]
  uri = "${HTTP_URL}"
  encoding.codec = "json"
  request.headers = {"X-API-Key" = "${HTTP_API_KEY}"}

FROM ghcr.io/superfly/fly-log-shipper:latest
COPY http.toml /etc/vector/sinks/

I started by following the Fly Blog post from earlier this year. Here is the fly.toml:

# fly.toml app configuration file generated for selective-logshipper on 2023-10-13T08:20:01-07:00
#
# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
#

app = "selective-logshipper"
primary_region = "sea"

[build]

[env]
  HTTP_URL = "provider"
  QUEUE = "selective-logs"
  SUBJECT = "logs.selective.>"

[[services]]
  protocol = ""
  internal_port = 8686

Any thoughts? Thanks in advanced

2

It was a config issue. Our provider requires: framing.method = "newline_delimited" in the http sink

3

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