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 README and documentation to support new topology input format, allowing explicit non-trace batch sources. Update CLI commands and examples to reflect the inclusion of topology files. Improve test coverage for topology discovery and ensure proper handling of provenance and overlays in the discovery process.
Copy file name to clipboardExpand all lines: README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Bering is a discovery and publishing layer for service topology and endpoint con
4
4
5
5
It supports two operating modes:
6
6
7
-
- deterministic batch discovery from trace files and directories
7
+
- deterministic batch discovery from trace files/directories or explicit topology input files
8
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.
@@ -40,6 +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/topology non-trace topology_api file loading and normalization
43
44
internal/connectors/otlp OTLP request decoding into normalized spans
44
45
internal/discovery source-agnostic discovery engine and overlay application
45
46
internal/model stable core model structs, semantic checks, canonical IO
Copy file name to clipboardExpand all lines: docs/architecture.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,8 @@ Bering now has two user-facing flows built on one normalized discovery core.
7
7
### Batch flow
8
8
9
9
1.`bering discover` loads trace JSON files or directories.
10
-
2.File inputs are normalized into the internal `traces.Span` shape.
11
-
3. The discovery engine infers services, edges, endpoints, confidence, and overlay-driven metadata.
10
+
2.Trace inputs are normalized into the internal `traces.Span` shape, while explicit `topology_api` inputs are normalized into the same downstream model and snapshot discovery contracts.
11
+
3. The discovery engine or adapter-specific builder produces services, edges, endpoints, confidence, and overlay-driven metadata.
12
12
4. Bering writes the stable `io.mb3r.bering.model` artifact.
13
13
5. Optional `--snapshot-out` also writes a `io.mb3r.bering.snapshot` envelope.
Bering also supports an explicit non-trace batch source: `topology_api`.
4
+
5
+
This is intended for cases where topology is already available from a topology API, service registry, mesh export, or another inventory source and you want Bering to publish the same model and snapshot artifacts without going through trace inference.
0 commit comments