FM / trace

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

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

Name	Size	Mode	Actions
internal/	-	0755	rm
attributes.d.ts	344	0644	edit dl rm
attributes.js	134	0644	edit dl rm
attributes.js.map	567	0644	edit dl rm
context-utils.d.ts	1275	0644	edit dl rm
context-utils.js	1644	0644	edit dl rm
context-utils.js.map	2969	0644	edit dl rm
invalid-span-constants.d.ts	364	0644	edit dl rm
invalid-span-constants.js	500	0644	edit dl rm
invalid-span-constants.js.map	996	0644	edit dl rm
link.d.ts	1295	0644	edit dl rm
link.js	128	0644	edit dl rm
link.js.map	1514	0644	edit dl rm
NonRecordingSpan.d.ts	1169	0644	edit dl rm
NonRecordingSpan.js	1371	0644	edit dl rm
NonRecordingSpan.js.map	2900	0644	edit dl rm
NoopTracer.d.ts	780	0644	edit dl rm
NoopTracer.js	2180	0644	edit dl rm
NoopTracer.js.map	4896	0644	edit dl rm
NoopTracerProvider.d.ts	511	0644	edit dl rm
NoopTracerProvider.js	449	0644	edit dl rm
NoopTracerProvider.js.map	999	0644	edit dl rm
ProxyTracer.d.ts	1209	0644	edit dl rm
ProxyTracer.js	1262	0644	edit dl rm
ProxyTracer.js.map	3286	0644	edit dl rm
ProxyTracerProvider.d.ts	1089	0644	edit dl rm
ProxyTracerProvider.js	1455	0644	edit dl rm
ProxyTracerProvider.js.map	2486	0644	edit dl rm
Sampler.d.ts	1600	0644	edit dl rm
Sampler.js	131	0644	edit dl rm
Sampler.js.map	1842	0644	edit dl rm
SamplingResult.d.ts	1824	0644	edit dl rm
SamplingResult.js	1029	0644	edit dl rm
SamplingResult.js.map	2199	0644	edit dl rm
span.d.ts	5019	0644	edit dl rm
span.js	128	0644	edit dl rm
span.js.map	5172	0644	edit dl rm
spancontext-utils.d.ts	804	0644	edit dl rm
spancontext-utils.js	2047	0644	edit dl rm
spancontext-utils.js.map	4684	0644	edit dl rm
SpanOptions.d.ts	755	0644	edit dl rm
SpanOptions.js	135	0644	edit dl rm
SpanOptions.js.map	972	0644	edit dl rm
span_context.d.ts	2145	0644	edit dl rm
span_context.js	136	0644	edit dl rm
span_context.js.map	2321	0644	edit dl rm
span_kind.d.ts	952	0644	edit dl rm
span_kind.js	1251	0644	edit dl rm
span_kind.js.map	1376	0644	edit dl rm
status.d.ts	605	0644	edit dl rm
status.js	687	0644	edit dl rm
status.js.map	971	0644	edit dl rm
tracer.d.ts	2695	0644	edit dl rm
tracer.js	130	0644	edit dl rm
tracer.js.map	2911	0644	edit dl rm
tracer_options.d.ts	267	0644	edit dl rm
tracer_options.js	138	0644	edit dl rm
tracer_options.js.map	482	0644	edit dl rm
tracer_provider.d.ts	878	0644	edit dl rm
tracer_provider.js	139	0644	edit dl rm
tracer_provider.js.map	1089	0644	edit dl rm
trace_flags.d.ts	234	0644	edit dl rm
trace_flags.js	441	0644	edit dl rm
trace_flags.js.map	592	0644	edit dl rm
trace_state.d.ts	1520	0644	edit dl rm
trace_state.js	135	0644	edit dl rm
trace_state.js.map	1862	0644	edit dl rm

Edit: /opt/canhelp/node_modules/@opentelemetry/api/build/esnext/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