-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support sending OpenTelemetry logs #13622
Comments
One outstanding question that needs to be answered is how we want to model the configuration for the sink, allowing for either HTTP or gRPC based sending. Perhaps something like: otel:
type: opentelemetry
inputs: ["source0"]
address: http://otelcol2:4318
protocol: grpc # grpc OR http
http:
path: "/custom/logs" # changing from the default "/v1/logs" path
tls:
# ... Generally want to ensure it's clear what options are valid for http vs grpc, or for both, as well as staying similar/familiar with other sinks. |
And there's another question, how to fulfill the opentelemetry proto object by vector Event model?
We'd better make sure vector outputs what it received. And If vector ingest data from file, kafka or any other non-otel sources, how to convert those data(EventLog) to otel proto object |
We have some inflight work that can help ease the translation between data models, but I think we'd start with something similar to our gelf encoder. |
Implementation plan
Config
|
Note to self: #21866 is a good first step. Keeping this open until we support gRPC. Format mapping will be left as an enhancement for later. |
Subtasks:
gRPC can be modeled after the
vector
(v2) sink.HTTP can refer to the
datadog
sinks.Ref: https://opentelemetry.io/docs/reference/specification/protocol/exporter/
Ref: https://opentelemetry.io/docs/reference/specification/protocol/otlp/
The text was updated successfully, but these errors were encountered: