OpenTelemetry Bot d680729c09 [chore] Prepare release 0.90.0 (#29543) | 1 year ago | |
---|---|---|
.. | ||
internal | 1 year ago | |
testdata | 2 years ago | |
Makefile | 5 years ago | |
README.md | 1 year ago | |
config.go | 1 year ago | |
config_test.go | 1 year ago | |
doc.go | 1 year ago | |
factory.go | 1 year ago | |
factory_test.go | 1 year ago | |
go.mod | 1 year ago | |
go.sum | 1 year ago | |
metadata.yaml | 1 year ago | |
trace_receiver.go | 1 year ago | |
trace_receiver_test.go | 1 year ago |
Status | |
---|---|
Stability | beta: traces |
Distributions | contrib, observiq, splunk, sumo |
Issues | |
Code Owners | @atoulme |
The SAPM receiver builds on the Jaeger proto. This allows the collector to receive traces from other collectors or the SignalFx Smart Agent. SAPM proto and some useful related utilities can be found here.
The following settings are required:
endpoint
(default = 0.0.0.0:7276
): Address and port that the SAPM
receiver should bind to.The following setting are optional:
access_token_passthrough
: (default = false
) Whether to preserve incoming
access token (X-Sf-Token
header value) as "com.splunk.signalfx.access_token"
trace resource attribute. Can be used in tandem with identical configuration option
for SAPM exporter to preserve trace origin.tls_settings
(no default): This is an optional object used to specify if TLS should
be used for incoming connections.
cert_file
: Specifies the certificate file to use for TLS connection.
Note: Both key_file
and cert_file
are required for TLS connection.key_file
: Specifies the key file to use for TLS connection. Note: Both
key_file
and cert_file
are required for TLS connection.Example:
receivers:
sapm:
endpoint: localhost:7276
access_token_passthrough: true
tls:
cert_file: /test.crt
key_file: /test.key
The full list of settings exposed for this receiver are documented here with detailed sample configurations here.