Marc Mintel
5397309103
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 20s
Build & Deploy / 🧪 QA (push) Failing after 34s
Build & Deploy / 🏗️ Build (push) Has started running
Build & Deploy / 🚀 Deploy (push) Has been cancelled
Build & Deploy / 🧪 Smoke Test (push) Has been cancelled
Build & Deploy / ⚡ Lighthouse (push) Has been cancelled
Build & Deploy / 🔔 Notify (push) Has been cancelled
26 lines
1.2 KiB
Plaintext
26 lines
1.2 KiB
Plaintext
import { SpanAttributes } from './attributes';
|
|
import { 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.
|
|
*/
|
|
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 |