In addition to the export type, this should be somehow specified inside of the OpenTelemetry exporter stage. This is a somehow odd situation, because these two properties aren’t core OpenTelemetry properties. I see two ways to achieve this:
Easierst: Just have it as kieker.tools.oteltransformer.stages.OpentelemetryExporterStage.ExplorViz_TokenId and .ExplorViz_Secret, and document that these are special properties
Create a specialized ExplorVizExporterStage again, that inherits from the OpenTelemetryExporterStage and also sets these both properties
We should discuss at the Kieker meeting how to address this and then implement it.
JIRA Issue: KIEKER-2001 Make ExplorViz Token Id and Secret Configurable Original Reporter: David Georg Reichelt
Currently, explorviz.token.id and explorviz.token.secret are hard-coded in the otel-transformer: https://github.com/kieker-monitoring/kieker/blob/main/tools/otel-transformer/src/kieker/tools/oteltransformer/stages/OpenTelemetryExporterStage.java#L196 This is only usable for demo purposes.
In addition to the export type, this should be somehow specified inside of the OpenTelemetry exporter stage. This is a somehow odd situation, because these two properties aren’t core OpenTelemetry properties. I see two ways to achieve this:
We should discuss at the Kieker meeting how to address this and then implement it.