FM / trace

/opt/canhelp/node_modules/@opentelemetry/api/build/src/trace/

/opt/canhelp/node_modules/@opentelemetry/api/build/src/trace

Name	Size	Mode	Actions
internal/	-	0755	rm
attributes.d.ts	344	0644	edit dl rm
attributes.js	200	0644	edit dl rm
attributes.js.map	568	0644	edit dl rm
context-utils.d.ts	1275	0644	edit dl rm
context-utils.js	2067	0644	edit dl rm
context-utils.js.map	2926	0644	edit dl rm
invalid-span-constants.d.ts	364	0644	edit dl rm
invalid-span-constants.js	686	0644	edit dl rm
invalid-span-constants.js.map	944	0644	edit dl rm
link.d.ts	1295	0644	edit dl rm
link.js	194	0644	edit dl rm
link.js.map	1515	0644	edit dl rm
NonRecordingSpan.d.ts	1169	0644	edit dl rm
NonRecordingSpan.js	1551	0644	edit dl rm
NonRecordingSpan.js.map	2879	0644	edit dl rm
NoopTracer.d.ts	780	0644	edit dl rm
NoopTracer.js	2444	0644	edit dl rm
NoopTracer.js.map	4791	0644	edit dl rm
NoopTracerProvider.d.ts	511	0644	edit dl rm
NoopTracerProvider.js	621	0644	edit dl rm
NoopTracerProvider.js.map	981	0644	edit dl rm
ProxyTracer.d.ts	1209	0644	edit dl rm
ProxyTracer.js	1413	0644	edit dl rm
ProxyTracer.js.map	3270	0644	edit dl rm
ProxyTracerProvider.d.ts	1089	0644	edit dl rm
ProxyTracerProvider.js	1655	0644	edit dl rm
ProxyTracerProvider.js.map	2438	0644	edit dl rm
Sampler.d.ts	1600	0644	edit dl rm
Sampler.js	197	0644	edit dl rm
Sampler.js.map	1843	0644	edit dl rm
SamplingResult.d.ts	1824	0644	edit dl rm
SamplingResult.js	1169	0644	edit dl rm
SamplingResult.js.map	2205	0644	edit dl rm
span.d.ts	5019	0644	edit dl rm
span.js	194	0644	edit dl rm
span.js.map	5173	0644	edit dl rm
spancontext-utils.d.ts	804	0644	edit dl rm
spancontext-utils.js	2446	0644	edit dl rm
spancontext-utils.js.map	4645	0644	edit dl rm
SpanOptions.d.ts	755	0644	edit dl rm
SpanOptions.js	201	0644	edit dl rm
SpanOptions.js.map	973	0644	edit dl rm
span_context.d.ts	2145	0644	edit dl rm
span_context.js	202	0644	edit dl rm
span_context.js.map	2322	0644	edit dl rm
span_kind.d.ts	952	0644	edit dl rm
span_kind.js	1375	0644	edit dl rm
span_kind.js.map	1381	0644	edit dl rm
status.d.ts	605	0644	edit dl rm
status.js	823	0644	edit dl rm
status.js.map	976	0644	edit dl rm
tracer.d.ts	2695	0644	edit dl rm
tracer.js	196	0644	edit dl rm
tracer.js.map	2912	0644	edit dl rm
tracer_options.d.ts	267	0644	edit dl rm
tracer_options.js	204	0644	edit dl rm
tracer_options.js.map	483	0644	edit dl rm
tracer_provider.d.ts	878	0644	edit dl rm
tracer_provider.js	205	0644	edit dl rm
tracer_provider.js.map	1090	0644	edit dl rm
trace_flags.d.ts	234	0644	edit dl rm
trace_flags.js	569	0644	edit dl rm
trace_flags.js.map	597	0644	edit dl rm
trace_state.d.ts	1520	0644	edit dl rm
trace_state.js	201	0644	edit dl rm
trace_state.js.map	1863	0644	edit dl rm

Edit: /opt/canhelp/node_modules/@opentelemetry/api/build/src/trace/link.d.ts (1295B)

import type { SpanAttributes } from './attributes';
import type { SpanContext } from './span_context';
/**
 * A pointer from the current {@link Span} to another span in the same trace or
 * in a different trace.
 * Few examples of Link usage.
 * 1. Batch Processing: A batch of elements may contain elements associated
 *    with one or more traces/spans. Since there can only be one parent
 *    SpanContext, Link is used to keep reference to SpanContext of all
 *    elements in the batch.
 * 2. Public Endpoint: A SpanContext in incoming client request on a public
 *    endpoint is untrusted from service provider perspective. In such case it
 *    is advisable to start a new trace with appropriate sampling decision.
 *    However, it is desirable to associate incoming SpanContext to new trace
 *    initiated on service provider side so two traces (from Client and from
 *    Service Provider) can be correlated.
 *
 * @since 1.0.0
 */
export interface Link {
    /** The {@link SpanContext} of a linked span. */
    context: SpanContext;
    /** A set of {@link SpanAttributes} on the link. */
    attributes?: SpanAttributes;
    /** Count of attributes of the link that were dropped due to collection limits */
    droppedAttributesCount?: number;
}
//# sourceMappingURL=link.d.ts.map

import type { SpanAttributes } from './attributes'; import type { SpanContext } from './span_context'; /** * A pointer from the current {@link Span} to another span in the same trace or * in a different trace. * Few examples of Link usage. * 1. Batch Processing: A batch of elements may contain elements associated * with one or more traces/spans. Since there can only be one parent * SpanContext, Link is used to keep reference to SpanContext of all * elements in the batch. * 2. Public Endpoint: A SpanContext in incoming client request on a public * endpoint is untrusted from service provider perspective. In such case it * is advisable to start a new trace with appropriate sampling decision. * However, it is desirable to associate incoming SpanContext to new trace * initiated on service provider side so two traces (from Client and from * Service Provider) can be correlated. * * @since 1.0.0 */ export interface Link { /** The {@link SpanContext} of a linked span. */ context: SpanContext; /** A set of {@link SpanAttributes} on the link. */ attributes?: SpanAttributes; /** Count of attributes of the link that were dropped due to collection limits */ droppedAttributesCount?: number; } //# sourceMappingURL=link.d.ts.map