22d6ecad2d
## What Parametrize the shard-matching prefix in `.github/scripts/o2-run-report.sh`. Adds a `SHARD_PREFIX` env (default `"e2e / "`) used everywhere the script identifies e2e shard jobs by name — the run-doc shard tallies (`shards_total/passed/failed/skipped`) and the per-shard rows written to `<STREAM>_shards`. ## Why The ENT **alpha1 cloud e2e** suite names its shard jobs `alpha1-e2e / <folder>`, which the hardcoded `e2e /` prefix did not match. This enabling change lets alpha1 (and any future differently-named suite) report per-shard rows to its own dedicated OpenObserve streams. See the companion ENT PR `test/alpha1-o2-reporting`. ## Safety The default `"e2e / "` (trailing space significant — `module` = job name minus prefix) preserves current OSS/regression behavior **exactly**. Verified with jq that the default still yields `module="Alerts"` for `"e2e / Alerts"` (no leading space) and that `"alpha1-e2e / "` yields `module="Alerts"` for the alpha1 job names. Cross-repo sibling: **o2-enterprise#`test/alpha1-o2-reporting`** (same branch slug). |
||
|---|---|---|
| .. | ||
| O2-REPORTING.md | ||
| assert_integrity.py | ||
| build-ci-matrix.js | ||
| check-db-schema-version.sh | ||
| extract-flaky.js | ||
| o2-report.sh | ||
| o2-run-report.sh | ||
| o2_metrics_resync.py | ||
| parse-api-junit.py | ||