You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying the ditto Helm chart as part of the IoT Packages cloud2edge chart, it would be useful to provide combined tracing support for Ditto and Hono. The straightforward thing to do for this, would be enabling tracing support in the Hono chart, and referencing the corresponding OTLP endpoint in the Ditto tracing configuration.
This would mean setting ditto.global.tracing.otelExporterOtlpEndpoint to http://c2e-jaeger-collector:4317 for example. But this only works if the used release name when deploying the cloud2edge chart is indeed c2e.
To support arbitrary release names, http://{{ .Release.Name }}-jaeger-collector:4317 would have to be used as otelExporterOtlpEndpoint value.
In order for this to work, the ditto Helm chart would just need to use the tpl function in the place where otelExporterOtlpEndpoint gets used. This is a feature request for doing so.
The text was updated successfully, but these errors were encountered:
calohmn
added a commit
to calohmn/ditto
that referenced
this issue
Sep 8, 2023
When deploying the ditto Helm chart as part of the IoT Packages cloud2edge chart, it would be useful to provide combined tracing support for Ditto and Hono. The straightforward thing to do for this, would be enabling tracing support in the Hono chart, and referencing the corresponding OTLP endpoint in the Ditto tracing configuration.
This would mean setting
ditto.global.tracing.otelExporterOtlpEndpoint
tohttp://c2e-jaeger-collector:4317
for example. But this only works if the used release name when deploying the cloud2edge chart is indeedc2e
.To support arbitrary release names,
http://{{ .Release.Name }}-jaeger-collector:4317
would have to be used asotelExporterOtlpEndpoint
value.In order for this to work, the ditto Helm chart would just need to use the
tpl
function in the place whereotelExporterOtlpEndpoint
gets used. This is a feature request for doing so.The text was updated successfully, but these errors were encountered: