Cross-repo workspace for Red Hat build of OpenTelemetry — shared specs, routing, and AI conventions.
| Repo | Purpose |
|---|---|
| opentelemetry-collector | Core collector |
| opentelemetry-collector-contrib | Collector contrib with all components |
| redhat-opentelemetry-collector | Red Hat distribution of the collector |
| opentelemetry-operator | Kubernetes operator |
| open-telemetry-opentelemetry-operator | Product/downstream fork of the operator, holds rhosdt-x.y branches used for QE product testing |
| os-observability-opentelemetry-operator | Legacy Konflux fork of the operator (rhosdt-3.7–3.11), still used by konflux-opentelemetry submodules |
| ocp-build-data | ART configuration for product builds, uses rhosdt-x.y branches |
| konflux-release-data | Konflux configuration repository in tenants-config/cluster/kflux-ocp-p01/tenants/art-rhosdt-tenant |
| konflux-opentelemetry | Downstream productization repository, contains all product components |
| konflux | Konflux release documentation and release payloads |
| openshift-docs | Documentation for the Red Hat build of OpenTelemetry |
| distributed-tracing-console-plugin | OpenShift console plugin for distributed tracing |
| logging-view-plugin | OpenShift console plugin for logging view |
| multicluster-observability-addon | Multi-cluster observability addon for ACM, includes OpenTelemetry |
| distributed-tracing-qe | Additional product test in tests/e2e-otel |
| release | OpenShift CI jobs for stage and downstream in ci-operator/config/openshift/open-telemetry-opentelemetry-operator |
Clone all repos into this directory:
make clone-reposPull latest changes in all repos:
make pull-reposAll specifications live in .ai/spec/. Start with .ai/spec/README.md for the product overview and reading guide. Use .ai/spec/how/repo-map.md to find which repo and spec file to update for a given concern.
- Create spec: a new spec files should be created with
/superpowers:brainstormingskill.As an input use product requirements or design ideas. The output should be a set of spec files in> /superpowers:brainstorming create or update specs for https://redhat.atlassian.net/browse/TRACING-6499. Also consider https://redhat.atlassian.net/browse/OBSDA-1454 which is the parent ticket. Do not commit and do not proceed with implementation..ai/spec/. - Create Jira tickets: in the same session run
/make-jira-from-specskill to create Jira tickets from the spec files. - Implementation: use
/superpowers:brainstormingskill with the Jira ticket as an input. After the implementation is done ask agent to update the spec files based on the implementation.
The /spec-first:init skill was used to create initial set of spec files. To install the spec-first plugin, run:
/plugin marketplace add joshuawilson/spec-first
/plugin install spec-first@spec-first-marketplaceExample prompt:
/spec-first:init create the specs. Document which features are supported and which not. The supported features are the ones that are documented in the docs. These features are either generally available (GA) or tech-preview (TP). If a feature is in the source code, but missing in docs, it is not supported.
- Jira: Project key
TRACINGonredhat.atlassian.net - Git workflow: Fork-based — push to your fork, PR against
origin/main, squash before pushing - Per-repo guides: Each repo has an
AGENTS.mdwith repo-specific conventions
To start QE release testing for a new RHOSDT OTEL version:
- Run the
/otel-qe-release-testing-epicskill with the release version (e.g.3.11) and the assignee for the work. It creates (or reuses) the Jira Epic that tracks release testing and populates it with the standard set of Tasks. - Follow the Epic and work through its Tasks — each Task's description points at the QE skill to use for that piece of testing.