-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[exporter/kafka] Logs with custom schema #12621
Comments
Pinging code owners: @pavolloffay @MovieStoreGuy |
This is probably depends on #12623 |
I think this warrants a further discussion than just applying to the KafkaExporter since this could also apply to the Kinesis Exporter, FileExporter and I am sure more in future. I need to think more about this because it also comes with a performance impact as well |
Thanks for comment! My implementation consists of 2 parts:
Custom schema implemented just by sending Attributes (which is dynamic map, could be constructed during Processing phase). So similar approach could be done in other exporters as well. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Is your feature request related to a problem? Please describe.
We want to send logs to Kafka using our custom schema.
Kafka exporter sends logs in defined LogsData format.
In our case we already have predefined schema for logs in our storage, so we want to send logs using our own schema.
Currently Kafka exporter does not allows to modify schema.
Describe the solution you'd like
I'm thinking about several different approaches how to implement custom schema for kafka exporter:
First approach is more generic I think.
It requires only attributes modification in standard opentelemetry-collector pipeline.
I'd like to hear what community thinks about it or if any other ideas.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: