signalfx / tracing-examples

Examples of using third-party tracers with SignalFx

ℹ️  SignalFx was acquired by Splunk in October 2019. See Splunk SignalFx for more information.

Tracing examples for Splunk Observability Cloud

This repository contains tracing examples for Splunk Observability Cloud, formerly known as SignalFx. Most of the examples use Splunk distributions of OpenTelemetry instrumentations. To learn more about OpenTelemetry and Splunk Observability Cloud, see the official documentation.

Supported formats

Splunk Observability Cloud and the Splunk Distribution of OpenTelemetry Collector can ingest tracing data in the following formats:

• OpenTelemetry Protocol or OTLP (Preferred)
• Zipkin v1 and v2 JSON
• Splunk APM Protocol (SAPM)

For more information, see Compatible span formats.

Instrumenting an application for Splunk

To instrument an application or service to send traces and spans to Splunk Observability Cloud, see Send traces to Splunk APM.

License

The example in this repository are licensed under the terms of the Apache Software License version 2.0. For more details, see the license file.

tracing-examples's Issues

Update the Java OpenTelemetry examples to be more self-contained

ideas:

• provide a pre-configured docker-compose setup for the collector that will send data to Splunk ingest

gunicorn app command needs to be updated

Step 5 of gunicorn python example needs to be updated. Instead of app.wsgi, it should be app:app for the startup parameters.

Java Compilation Error

Get an "Execution failed for task ':compileJava'. > Could not find tools.jar." error during the Build the example service section of Part 1 of the profiling workshop that this post resolved for me. I am on Monterey but it still worked to get past that error.

The example ""zipkin-brave-java-spring-boot-web" still sends traces to Zipkin...

I built the example as is and configured the ingest and token, but the spans apears to be sent to a default local zipkin server instead of to SignalFX:

I/O error on POST request for "http://localhost:9411/api/v1/spans":

Application.properties:
opentracing.reporter.signalfx.ingest_url=http://localhost:9080/v1/trace
(this is address of my Smart agent w/ trace listener enabled...

environment name

How do I configure the environment name in lambda function from where the traces are coming..?
by default it takes unknown

I have a lambda function that reports to /v2/trace endpoint..(no smart gateway and no opentelemetry configured)

Instruction update required for opentelemetry-tracing/opentelemetry-python-tracing/flask-and-uwsgi/

Could not install requirements.txt.

My environment is

• Python 3.10.0
• pip 21.2.3

Falcon Example

Hey guys, any particular reason the falcon example uses manual instrumentation in the /hello endpoint?
It should be automatically instrumented. Am I missing something?