You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhance runtime service to support optional OTLP/gRPC spans alongside OTLP/HTTP. Update configuration to include gRPC listener address and modify documentation to reflect new capabilities. Improve test coverage for gRPC functionality and ensure source summary handling in the ingestion process.
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Bering is a discovery and publishing layer for service topology and endpoint con
5
5
It supports two operating modes:
6
6
7
7
- deterministic batch discovery from trace files and directories
8
-
- long-running runtime discovery that accepts OTLP/HTTP spans and publishes rolling snapshot envelopes for observability consumers
8
+
- long-running runtime discovery that accepts OTLP/HTTP and optional OTLP/gRPC spans and publishes rolling snapshot envelopes for observability consumers
9
9
10
10
Bering owns discovery and discovery-side public contracts. It does not own simulation, gating, chaos execution, or policy decisions.
11
11
@@ -40,7 +40,7 @@ cmd/bering CLI entrypoint
40
40
internal/app command wiring
41
41
internal/config serve-mode config parsing and validation
42
42
internal/connectors/traces file/dir trace loading and normalization
43
-
internal/connectors/otlp OTLP/HTTP request decoding into normalized spans
43
+
internal/connectors/otlp OTLP request decoding into normalized spans
44
44
internal/discovery source-agnostic discovery engine and overlay application
45
45
internal/model stable core model structs, semantic checks, canonical IO
@@ -100,11 +100,12 @@ go run ./cmd/bering serve --config configs/serve.sample.yaml
100
100
The runtime service exposes:
101
101
102
102
-`POST /v1/traces` for OTLP/HTTP trace ingest
103
+
- OTLP/gRPC trace export service on the configured gRPC address
103
104
-`GET /healthz`
104
105
-`GET /readyz`
105
106
-`GET /metrics`
106
107
107
-
The primary integration path is standard OpenTelemetry Collector or SDK exporters sending spans to Bering over OTLP/HTTP. No custom Collector build is required.
108
+
The primary integration path remains standard OpenTelemetry Collector or SDK exporters sending spans to Bering over OTLP/HTTP. OTLP/gRPC is also supported for grpc-first collector topologies. No custom Collector build is required.
0 commit comments