What would you like to be added:
Support for multiple backends and authorization schemes.
Why is this needed:
Currently, the datasink CR is mostly coupled with Dynatrace as backend or another backend using token authorization with the same auth header (unlikely). If the backend does not support token authentication but cert based one the integration would fail (example BTP cloud logging). As a workaround users could deploy a OTEL collector in-between and push telemetry to various backends but this requires users to create the OTEL collector themselves using cluster admin roles (in case of MCPs)
What would you like to be added:
Support for multiple backends and authorization schemes.
Why is this needed:
Currently, the datasink CR is mostly coupled with Dynatrace as backend or another backend using token authorization with the same auth header (unlikely). If the backend does not support token authentication but cert based one the integration would fail (example BTP cloud logging). As a workaround users could deploy a OTEL collector in-between and push telemetry to various backends but this requires users to create the OTEL collector themselves using cluster admin roles (in case of MCPs)