Skip to main content

Review the O-RAN Telemetry Reference

This path inspects repository artifacts. It does not collect an O-RAN protocol, deploy to OpenShift, or contact any destination.

Prerequisites​

  • A checkout of this repository
  • A shell with sed and rg
  • No RAN, cluster, broker, or analytics credentials

Run the inspection​

From the repository root:

test -f static/pipelines/oran-telco-pipeline.yaml
test -f examples/integrations/oran-input.yaml
sed -n '1,80p' examples/integrations/oran-input.yaml
rg -n 'input:|mapping:|broker:|kafka:|file:' \
  static/pipelines/oran-telco-pipeline.yaml

Expected output​

Both file checks exit successfully. The fixture shows authored telemetry, and the final command identifies source, transformation, and external destination boundaries.

Cleanup​

No files or external resources are created.

Common failures​

  • A missing file means the checkout does not contain the referenced artifact.
  • An empty search means the combined reference changed; inspect it directly before updating the walkthrough.
  • The fixture and mappings do not validate network thresholds or destination contracts.

Next: Inspect the source boundary.