open-telemetry/opentelemetry-cpp

This issue covers resolving the cppcoreguidelines-pro-type-const-cast warnings. clang-tidy warnings (click to expand) File Line Message opentelemetry-cpp/examples/http/server.cc 55 do not use const_cast to remove const qualifier opentelemetry-cpp/ext/include/opentelemetry/ext/http/client/curl/http_operation_curl.h 297 do not use const_cast to remove const qualifier opentelemetry-cpp/ext/src/http/client/curl/http_operation_curl.cc 915 do not use const_cast to remove const qualifier opentelemetry-cpp/ext/src/http/client/curl/http_operation_curl.cc 957 do not use const_cast to remove const qualifier opentelemetry-cpp/ext/src/http/client/curl/http_operation_curl.cc 1005 do not use const_cast to remove const qualifier opentelemetry-cpp/ext/test/w3c_tracecontext_http_test_server/main.cc 206 do not use const_cast to remove const qualifier opentelemetry-cpp/sdk/include/opentelemetry/sdk/common/circular_buffer.h 43 do not use const_cast to remove const qualifier opentelemet

This issue covers resolving the 20 modernize-use-emplace warnings: clang-tidy warnings (click to expand) File Line Message opentelemetry-cpp/api/test/baggage/propagation/baggage_propagator_test.cc 90 use emplace_back instead of push_back opentelemetry-cpp/api/test/context/propagation/composite_propagator_test.cc 145 use emplace_back instead of push_back opentelemetry-cpp/api/test/context/runtime_context_test.cc 127 use emplace_back instead of push_back opentelemetry-cpp/api/test/nostd/shared_ptr_test.cc 224 use emplace_back instead of push_back opentelemetry-cpp/api/test/trace/propagation/http_text_format_test.cc 265 use emplace_back instead of push_back opentelemetry-cpp/api/test/trace/propagation/jaeger_propagation_test.cc 194 use emplace_back instead of push_back opentelemetry-cpp/examples/multithreaded/main.cc 63 use emplace_back instead of push_back opentelemetry-cpp/exporters/otlp/src/otlp_file_client.cc 568 use emplace_back instead of push_back opentelemet

Configuration of General Attribute Limits Background: The configuration schema includes a general attribute_limits element at the same level as the signal providers. This element defines limits for attribute count and length that should be used by the tracer and logger provider if their limits elements are not configured. attribute_limits: $ref: "#/$defs/AttributeLimits" description: | Configure general attribute limits. See also tracer_provider.limits, logger_provider.limits. The YAML parser supports attribute_limits, but the SdkBuilder currently does not pass them into the builders for the Tracer and Logger providers. As a result these values are ignored. See: opentelemetry-cpp/sdk/src/configuration/sdk_builder.cc Line 2641 in b603742 OTEL_INTERNAL_LOG_WARN("attribute_limits not supported, ignoring"); The spec requires the following limit behavior: If bot

Background: The schema defines resource.attributes_list as the primary method to support reading strings following the format of the OTEL_RESOURCE_ATTRIBUTES env variable when creating the Resource with declarative configuration. resource: # Read resource attributes from the OTEL_RESOURCE_ATTRIBUTES environment variable. # This aligns well with the OpenTelemetry Operator and other deployment methods. attributes_list: ${OTEL_RESOURCE_ATTRIBUTES} Resource Schema: resource: attributes_list: type: - string - "null" description: | Configure resource attributes. Entries have lower priority than entries from .resource.attributes. The value is a list of comma separated key-value pairs matching the format of OTEL_RESOURCE_ATTRIBUTES. See https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md#general-sdk-configuration for details. defaultBehavior: no resource attributes are adde

Process Entities - Required and Recommended Attributes This ticket is to add the remaining required and recommended attributes from Process Entities to the Process Resource Detector. PRs against this ticket may be scoped to one or more attributes on one or more platforms (Linux, macOS, Windows). All PRs should update the resource_detectors/README with the attribute(s) added, platform(s) supported, and known limitations. Process Entity (process) Attribute Type Description Requirement Level process.creation.time string Date/time the process was created (ISO 8601) Required process.owner string Username of the user that owns the process Recommended Process Executable Entity (process.executable) Attribute Type Description Requirement Level process.executable.build_id.htlhash string Deterministic build ID (SHA256 of first/last 4096 bytes + length) Required process.executable.name string Base name of the process executable — note: process.executable.path is already im