vectordotdev / vectordotdev/vector

Enable opentelemetry sink to send data to to all available endpoints

Open
#25,969 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

sink: opentelemetry
Dominant language
Rust
Stars
22.6k
Forks
2.3k
Avg merge
1d 7h
Merged PRs (30d)
146

Description

A note for the community
Use Cases

Right now when you specify opentelemetry endpoint URL, sink supports only concrete endpoint type (e.g. /logs)
This would be fine if there'd be grpc support, but for HTTP protocol it would be desirable to have option to support base otlp endpoint and send data to <BASE>/logs by default
Otherwise if user needs to propagate metrics and logs, he is expected to declare sink multiple times

Attempted Solutions

This is not a bug, but rather a suggestion.
Right now user is expected to declare separate OTLP sink for every supported type of event (i.e. logs/metrics)

Proposal
  1. Change interface to support base endpoint
  2. Introduce new optional parameters:
    • protocol.uri_suffix_logs with default value /logs
    • protocol.uri_suffix_metrics with default value /metrics
    • protocol.uri_suffix_traces with default value `/traces
References

No response

Version

vector 0.57.0 (x86_64-unknown-linux-musl 8832452 2026-07-14 20:58:30.491174540)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the OpenTelemetry sink and its protocol endpoint configuration, then trace how logs, metrics, and traces currently choose their endpoint paths. Implement support for a base OTLP endpoint and the proposed protocol.uri_suffix_logs, protocol.uri_suffix_metrics, and protocol.uri_suffix_traces options, with the documented defaults. Done means one sink can send each supported event type to its corresponding endpoint without separate sink declarations.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.