Phase 0: Python Warm-up

2. Instrument with OBI

2 min

Now add APM tracing to this running app without touching a single line of code.

Download OBI

Download the pre-built OBI binary from the GitHub releases page :

bash 
cd ~/workshop/obi/01-obi-python

sudo env \
  OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://ingest.${REALM}.signalfx.com:443" \
  OTEL_EXPORTER_OTLP_TRACES_PROTOCOL="grpc" \
  OTEL_EXPORTER_OTLP_HEADERS="X-SF-Token=${ACCESS_TOKEN}" \
  OTEL_SERVICE_NAME="warmup-app" \
  OTEL_RESOURCE_ATTRIBUTES="deployment.environment=ebpf-bare-app,host.name=${INSTANCE}" \
  OTEL_EBPF_OPEN_PORT=5150 \
  ./obi

Run OBI

Exercise

In a separate terminal, run OBI with sudo. Replace the three placeholders with your realm, token, and hostname from the previous step (this may take a minute or two to complete):

bash 
cd ~/workshop/obi/01-obi-python

sudo env \
  OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://ingest.${REALM}.signalfx.com:443" \
  OTEL_EXPORTER_OTLP_TRACES_PROTOCOL="grpc" \
  OTEL_EXPORTER_OTLP_HEADERS="X-SF-Token=${ACCESS_TOKEN}" \
  OTEL_SERVICE_NAME="warmup-app" \
  OTEL_RESOURCE_ATTRIBUTES="deployment.environment=ebpf-bare-app,host.name=${INSTANCE}" \
  OTEL_EBPF_OPEN_PORT=5150 \
  ./obi

What Do These Variables Do?

VariablePurpose
sudoeBPF probes require root/kernel access
OTEL_EXPORTER_OTLP_TRACES_ENDPOINTFull URL for Splunk’s OTLP trace ingest. The per-signal env var sends to this URL exactly the base OTEL_EXPORTER_OTLP_ENDPOINT would append /v1/traces which doesn’t match Splunk’s path
OTEL_EXPORTER_OTLP_HEADERSAuth header for Splunk
OTEL_SERVICE_NAMEThe service name that appears in Splunk APM
OTEL_RESOURCE_ATTRIBUTESSets deployment.environment and host.name on every trace so you can filter to your data
OTEL_EBPF_OPEN_PORTTells OBI to instrument the process listening on port 5150

Note

You may see warnings like failed to upload metrics: 404 Not Found in the OBI logs. This is expected Splunk’s direct ingest doesn’t have a standard OTLP metrics endpoint. The traces still export correctly. In Phase 2, a collector handles both traces and metrics properly.

Generate Traffic

Go back to your first terminal and generate some requests:

bash 
for i in $(seq 1 20); do curl -s "http://localhost:5150/hello"; sleep 1; done

NOTE: If you get a 404 error double check that there is no \ appended to the url you are curling. In some termings the ; will attempt to escape and cause an invalid url

Last Modified ·