Specification

Recently changed requirements

• v1.60.0sdk.md#emit-a-logrecordMUST added: Enabled: If the Logger is not enabled (i.e. LoggerConfig.enabled is false), the log record MUST be dropped.
• v1.60.0sdk.md#createMUST added: When both Entities and Attributes are provided in the create method, the system MUST behave as if a Resource is created with just Attributes and then merges with another Resource created with just Entities.
• v1.60.0sdk.md#mergeMUST added: If either resource contains Entities then merge behavior with Entiites MUST be used, otherwise merge behavior without Entities MUST be used.
• v1.60.0sdk.md#merge-behavior-with-entitiesMUST added: When either Resource contains entities, the merge operation MUST follow the resource data model's merge algorithm.
• v1.60.0sdk.md#merge-behavior-with-entitiesMUST added: The resulting SchemaURL MUST match the behavior defined in the merge algorithm.
• v1.60.0sdk.md#retrieve-attributesMUST added: When entities are enabled and present for the Resource, this list MUST include all attributes, including those associated with entities.
• v1.59.0env-carriers.md#process-spawningMUST NOT removed: The language implementations MUST NOT handle spawning processes.
• v1.59.0env-carriers.md#propagator-mechanismsMUST NOT added: Language implementations MUST NOT spawn child processes as part of environment variable context propagation.
• v1.59.0env-carriers.md#propagator-mechanismsSHOULD added: Language implementations SHOULD document operational guidance, including initialization-time extraction, child process environment handling, and security considerations.
• v1.59.0sdk.md#getsamplingintentSHOULD added: The calling CompositeSampler SHOULD update the threshold of the outgoing TraceState, as described above.
• v1.58.0prometheus_and_openmetrics.md#histograms-1MUST removed: The final bucket metric MUST have an +Inf threshold.
• v1.58.0README.md#arraysSHOULD added: Array elements SHOULD be represented as JSON values using the following rules:
• v1.58.0README.md#attribute-collection-representation-for-non-otlpRECOMMENDED added: For non-OTLP protocols that need to represent an Attribute Collection as a string, the RECOMMENDED form is a JSON object.
• v1.58.0README.md#attribute-collection-representation-for-non-otlpSHOULD added: Each attribute key SHOULD be represented as a JSON object member name.
• v1.58.0README.md#attribute-collection-representation-for-non-otlpSHOULD added: Each attribute value SHOULD be represented as the corresponding JSON object member value and follow the encoding rules defined in AnyValue representation for non-OTLP protocols, as it would be represented as an element ...
• v1.58.0README.md#attribute-representation-for-non-otlpRECOMMENDED added: For non-OTLP protocols that need to represent a single Attribute as a string, the RECOMMENDED form is a JSON object containing a single name/value pair (member).