mirror of
https://github.com/oven-sh/setup-bun.git
synced 2025-07-19 21:18:22 +02:00
feat: add @actions/cache
This commit is contained in:
parent
b15fb7d098
commit
16e8c96a41
1932 changed files with 261172 additions and 10 deletions
24
node_modules/@opentelemetry/api/build/esm/trace/link.d.ts
generated
vendored
Normal file
24
node_modules/@opentelemetry/api/build/esm/trace/link.d.ts
generated
vendored
Normal file
|
@ -0,0 +1,24 @@
|
|||
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;
|
||||
}
|
||||
//# sourceMappingURL=link.d.ts.map
|
Loading…
Add table
Add a link
Reference in a new issue