bolt
SWiPE 3.0.0 login Sign in
transform

OTel Transformer — Online Boutique

Generate OpenTelemetry collector configurations for your vertical

category

Service Name Mappings

Endpoint Mappings

Edit the mapped endpoint values. These control how gRPC service/method names appear in traces.

conversion_path

Select a vertical to load endpoint mappings.

Original Endpoint Mapped Endpoint

Deployment

Using a Splunk4Ninjas — Observability workshop instance, deploy this configuration to transform your telemetry data.

1. Add the Helm chart repository:

helm repo add splunk-otel-collector-chart https://signalfx.github.io/splunk-otel-collector-chart && helm repo update

2. Download the YAML below and save as values.yaml in /home/splunk/workshop/k3s/

3. Deploy the collector:

helm install splunk-otel-collector \
  --set="splunkObservability.realm=$REALM" \
  --set="splunkObservability.accessToken=$ACCESS_TOKEN" \
  --set="clusterName=$INSTANCE-k3s-cluster" \
  --set="agent.service.enabled=true" \
  --set="environment=$INSTANCE-workshop" \
  --set="splunkPlatform.endpoint=$HEC_URL" \
  --set="splunkPlatform.token=$HEC_TOKEN" \
  --set="splunkPlatform.index=splunk4rookies-workshop" \
  splunk-otel-collector-chart/splunk-otel-collector \
  -f ~/workshop/k3s/otel-collector.yaml \
  -f ~/workshop/k3s/values.yaml

4. Deploy the Online Boutique application:

kubectl apply -f ~/workshop/apm/deployment.yaml

Service Graph

account_tree

Click Generate to see the service topology.

YAML output will appear here after generation.