vectordotdev/vector

Configuration error. error=Sink "loki": invalid format

Open

#10,980 opened on Jan 22, 2022

View on GitHub
 (1 comment) (4 reactions) (0 assignees)Rust (21,837 stars) (2,126 forks)batch import
good first issuesink: loki

Description

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Current Vector Version

vector 0.19.0 (x86_64-unknown-linux-gnu da60b55 2021-12-28)

Use-cases

[sources.generate_syslog]
type = "demo_logs"
format = "syslog"

[sinks.loki]
type = "loki"
inputs = ["generate_syslog"]
labels.host="localhost"
endpoint = "something-with-a-typo-that-is-hard-to-notice"
encoding.codec = "logfmt"

output nothing more useful than

2022-01-22T01:13:22.313577Z ERROR vector::topology: Configuration error. error=Sink "loki": invalid format

Proposal

A better error message that actually says what's wrong. Like "invalid format: endpoint" or something like that.

Contributor guide

Tech stack
rust
Domain
observability
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
RustVector sink configurationLoki sink code
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the Loki sink configuration validation in src/sinks/loki/config.rs to find where the 'invalid format' error is generated. Modify the error message to include the specific field name or reason, such as 'invalid format: endpoint'. Also check the topology error handling in src/topology/mod.rs to ensure better error propagation.