SignalFx Developers Guide

Developer Home

Product Docs

SignalFx

Send µAPM PG Tracing Data API

IMPORTANT: This documentation is for the original SignalFx Microservices APM product released in 2019 that is now known as Microservice APM Previous Generation (µAPM PG). The developer interface for the current µAPM product, released on March 31, 2020, is not available.

API for sending Microservices APM Previous Generation (µAPM PG) tracing data to SignalFx

Send Tracing Data

Sends tracing data to SignalFx

Sends Microservices APM Previous Generation (µAPM PG) tracing data to SignalFx. The µAPM PG API accepts output from the following tracing frameworks:

  • Zipkin JSON v1 and JSON v2:
    • Set the Content-Type header parameter for the request to application/json.
    • In your request body, send an array of Span objects. You can find the format of a JSON v2 Span in the REST API documentation for the Zipkin v2 API hosted on SwaggerHub.
  • Jaeger Thrift:
    • Set the Content-Type header parameter to application/x-thrift.
    • In your request body, send a list of Span structs. You can find the format of a Span struct in the file jaeger.thrift, in the GitHub repo for Jaeger tracing.
header Parameters
X-SF-TOKEN
required
string

Authentication token. Must be an org token (referred to as an access token in the web UI)

Content-Type
required
string

Format of the request payload:

  • For Zipkin JSON1 and JSON2 data, use application/json
  • For Jaeger Thrift data, use application/x-thrift

Responses

Response Schema: application/json
object

Key-value pairs containing information about invalid spans:

  • key: String containing the reason the span was invalid
  • value: Array of span IDs that were invalid for this reason
valid
integer <int64>

Count of valid spans received

Response samples

Content type
application/json
{
  • "invalid":
    {
    },
  • "valid": 0
}

© Copyright 2020 Splunk, Inc.

Third-party license information