[READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. (grpc依赖)

update-envoy[bot] f5b171e919 opentelemetry tracer: add support for environment resource detector (#29547 ) Commit Message: Allow specifying resource detectors for the OpenTelemetry tracer via a new configuration resource_detectors. The resource detector reads from the env variable OTEL_RESOURCE_ATTRIBUTES which is defined by the OTel specification. The detector returns a resource object populated with the detected attributes, which is sent as part of the OTLP request. Additional Description: This PR adds the "foundation" for building other resource detectors in Envoy. It is based on the OTel collector implementation. Users can configure multiple resource detectors, and they work together to "merge" all the detected attributes into a single resource object, which is then part of the OTLP message exported. Risk Level: Low Testing: Multiple unit tests, that cover all new code/scenarios. I also did manual testing, running Envoy locally with the OTel tracer + env resource detector enabled. Resource attributes detected from my environment is successfully exported as seen in the Jaeger screenshot. resource-detectors-env-jaeger Docs Changes: Not sure if I should add/where. Happy to do it. Release Notes: N/A Platform Specific Features: N/A [Optional Runtime guard:] N/A [Optional Fixes #28929] Here is how the new config is used: tracing: provider: name: envoy.tracers.opentelemetry typed_config: "@type": type.googleapis.com/envoy.config.trace.v3.OpenTelemetryConfig grpc_service: envoy_grpc: cluster_name: opentelemetry_collector timeout: 0.250s service_name: envoy-gRPC-exporter resource_detectors: # --> NEW CONFIG - name: envoy.tracers.opentelemetry.resource_detectors.environment typed_config: "@type": type.googleapis.com/envoy.extensions.tracers.opentelemetry.resource_detectors.v3.EnvironmentResourceDetectorConfig Signed-off-by: Joao Grassi <joao.grassi@dynatrace.com> Mirrored from https://github.com/envoyproxy/envoy @ 4eaa1f866164eee5d51e46406bcb31d8dec99bdd		1 year ago
.circleci	ci: remove docs/format jobs. (#619 )	7 years ago
.github/workflows	ci/sync: Use app to push changes (#629 )	2 years ago
bazel	deps/api: Bump `com_github_bufbuild_buf` -> 1.27.1 (#30390 )	1 year ago
ci	ci/sync: Use app to push changes (#629 )	2 years ago
contrib/envoy/extensions	generic proxy refactoring part 2: move upstream binding to router filter (#30265 )	1 year ago
envoy	opentelemetry tracer: add support for environment resource detector (#29547 )	1 year ago
examples/service_envoy	Add license declarations to some BUILD files. (#223 )	7 years ago
test	bazel: update to v5.0.0 (#19706 )	3 years ago
tools	tap: Fix the failure of protobuf to PCAP generation (#28180 )	1 year ago
versioning	opentelemetry tracer: add support for environment resource detector (#29547 )	1 year ago
.clang-format	adding check_format and fix_format (#300 )	7 years ago
.gitignore	validate: initial constraints support. (#226 )	7 years ago
API_VERSIONING.md	docs: minor fixes to API docs (#30480 )	1 year ago
BUILD	opentelemetry tracer: add support for environment resource detector (#29547 )	1 year ago
CONTRIBUTING.md	docs: Improve builds for Envoy and mobile (stamping) (#29887 )	1 year ago
LICENSE	Add Apache 2.0 LICENSE file. (#21 )	8 years ago
README.md	Docs: replace broken link in api/README.md (#15423 )	4 years ago
STYLE.md	docs: minor fixes to API docs (#30480 )	1 year ago
buf.lock	deps: Bump `com_github_bufbuild_buf` -> 1.13.1 (#25453 )	2 years ago
buf.yaml	buf/api: Fix warning about missing import (#28782 )	1 year ago
go.mod	golang filter: move go.mod & go.sum to the root directory. (#26606 )	2 years ago
review_checklist.md	repo: Update references - master -> main (#15190 )	4 years ago

README.md

Data plane API

This tree hosts the configuration and APIs that drive Envoy. The APIs are also in some cases used by other proxy solutions that aim to interoperate with management systems and configuration generators that are built against this standard. Thus, we consider these a set of universal data plane APIs. See this blog post for more information on the universal data plane concept.

Repository structure

The API tree can be found at two locations:

https://github.com/envoyproxy/envoy/tree/main/api - canonical read/write home for the APIs.
https://github.com/envoyproxy/data-plane-api - read-only mirror of https://github.com/envoyproxy/envoy/tree/main/api, providing the ability to consume the data plane APIs without the Envoy implementation.

README.md

Data plane API

Repository structure

Further API reading