[Support] - Vector Support Thread - coreylane repo

[coreylane]

Overview: Support for vector CA available in the coreylane repo.

Application: Vector - GitHub Project

Docker Hub: https://hub.docker.com/r/timberio/vector/

Template GitHub: https://github.com/coreylane/unraid-ca-templates

 

How do I ingest/collect Unraid logs using Vector? 

Vector can be used with logs of any kind, but my original intention was to use Vector for ingestion of Unraid logs. Please see the below configuration guides for instructions on ingesting Unraid logs with Vector. 

 

Unraid Docker Logs

To ingest Unraid's docker logs using Vector, the container needs read-only access to the unix socket Docker listens on. The default in Unraid is /var/run/docker.sock

 

Add the below path configuration to the Vector container:

 

 

Unraid syslog

To ingest Unraid's system logs using Vector, the container needs read-only access to the syslog file. The default in Unraid is /var/log/syslog

 

Add the below path configuration to the Vector container:

 

 

Vector configuration

When the container paths are setup, the final step is to provide a vector.toml configuration defining the desired log sources and destinations (sinks) where the logs should be shipped. Below is a very simple example Vector configuration that ingests docker logs and unraid syslogs and sends them to the cloud based log service Logtail. 

 

Example /mnt/user/appdata/vector.toml

[sources.docker_logs]
type = "docker_logs"

[sources.unraid_logs]
type = "file"
include = ["/var/log/syslog"]

[sinks.logtail_http]
type = "http"
method = "post"
uri = "https://in.logtail.com/"
encoding.codec = "json"
auth.strategy = "bearer"
auth.token = "XXXXXXXXXXXXXXXXXXXXXX"
inputs = ["docker_logs", "unraid_logs"]

 

New Relic Configuration

The below vector.toml snippit will ship your logs to new relic

 

[sinks.new_relic]
type = "new_relic"
inputs = ["docker_logs", "unraid_logs"]
account_id = "123456"
api = "logs"
license_key = "XXXXXXXXXXXXX"

 

Edited May 19, 2023 by coreylane
adding new relic

[Steve Croft]

Hey, my Vector docker has recently stopped working despite no configuration changes.

 

It looks like its failing to recognise the vector.toml configuration file being present and potentially expecting a .yaml or .json version. All three appear valid according to the docs.

https://vector.dev/docs/reference/configuration/

 

Error

2023-12-04T22:36:01.486966Z ERROR vector::config::loading: Config file not found in path. path="/etc/vector/vector.yaml"

 

[coreylane]

Thank you for reporting this. I'm having the same issue.

 

This behavior was changed in Vector 0.34. I will work on a fix to the unraid template now.

https://vector.dev/highlights/2023-11-07-0-34-0-upgrade-guide/#default-config-location-change
 

Quote

 

Default config location change

The default config location is now /etc/vector/vector.yaml rather than /etc/vector/vector.toml. This is part of the migration to YAML as Vector’s preferred configuration language (though TOML and JSON will still be supported for the forseeable future). If you need Vector to load /etc/vector/vector.toml you must now specify --config /etc/vector/vector.toml or VECTOR_CONFIG=/etc/vector/vector.toml

 

 

[coreylane]

20 hours ago, Steve Croft said:

Error

2023-12-04T22:36:01.486966Z ERROR vector::config::loading: Config file not found in path. path="/etc/vector/vector.yaml"

 

 

Hi Steve, you can fix this by adding a new environment variable to the docker container configuration in Unraid. Please see screenshots below

 

Type: Variable

Key: VECTOR_CONFIG

Value: /etc/vector/vector.toml

 

 

Edited December 5, 2023 by coreylane

[Steve Croft]

Thanks @coreylane all sorted!