Telemetry Configurations Settings

A name to identify the application in the telemetry data store. In the visualization software, you can identify your application using the Service Name.

The default service name is default.

(Optional) A sampler strategy helps control the volume of telemetry data that you want to export.

• always_on - Use this strategy to send every span to the export pipeline.

• always_off - Use this strategy to ensure that no spans are sent to the export pipeline.

• traceidratio - Use this strategy to send a specified fraction of spans based on their TraceId. You can specify the fraction value in the TraceId Ratio field.

• parentbased_always_on - When the request is coming from another application or service, use this strategy to use the sampling algorithm of the parent application or service, otherwise to send every span to the export pipeline.

• parentbased_always_off - When the request is coming from another application or service, use this strategy to use the sampling algorithm of the parent application or service, otherwise not to send any span to the export pipeline.

• parentbased_traceidratio - When the request is coming from another application or service, use this strategy to use the sampling algorithm of the parent application or service otherwise to send a specified fraction of spans based on their TraceId. You can specify the fraction value in the TraceId Ratio field.

The default value is always_on.

Enabled only when the traceidratio or parentbased_traceidratio sampler strategy is selected. A sampling ratio must be specified to a value between 0.0 to 1.0. The 0.0 value specifies that no spans are to be sent while the 1.0 value specifies that all spans are sent. For example, to send 50% of spans to the export pipeline, select the value as 0.5.

The default value is 1.0.

Enter a comma-separated list of propagators to be used to serialize and deserialize the context. Click the Browse button to open the list of available propagators. You can select one or more than one propagator for your application. The following propagators are supported exclusively in TIBCO BusinessEvents:

• tracecontext

• baggage

• b3

• b3multi

• jaeger

• ottrace

The default propagator is tracecontext.

For details about propagators, see OpenTelemetry documentation.

(Optional) By default all resources (/) are enabled for tracing. You can specify which resources need to be traced. All Resources starting with the URI specified will be enabled for tracing. There is AND operation between Enable Resource list and Disabled Resource list.

For example: If Enabled Resource List consist of URI: /Rules/Order/CreateOrderRule and Disabled Resource List Consist of URI: /Rules/Order. In this case, all rules starting with URI /Rules/Order are disabled for tracing. The Rule /Rules/Order/CreateOrderRule is also not enabled for tracing.

(Optional) Add resources here that you do not want to trace. You can use the full URI of rule, rule function, or destination, or partial paths to ignore all resources starting with that path. The list could also be updated through JMX at runtime.

(Optional) Span exporter exports the telemetry data to the specified collector. The following options are provided as span exporter:

• None

• OTLP (OpenTelemetry collector)

• Jaeger

• Zipkin

The default value is None.

The endpoint URL of the selected Span Exporter.

This field is not displayed when the Span Exporter value is None.

The request timeout (in milliseconds) for the selected Span Exporter.

This field is not displayed when the Span Exporter value is None.

Provide comma-separated key-value pairs as headers with the equals to symbol = separating the key and value.

This field is displayed when the Span Exporter value is OTLP.

Select the checkbox to enable the secured connection.

This field is displayed when the Span Exporter value is OTLP.