Surface OTLP export failures in observability step summary#32761
Merged
pelikhan merged 2 commits intoMay 17, 2026
Conversation
8 tasks
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add OTLP export failure visibility in workflow step summary
Surface OTLP export failures in observability step summary
May 17, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request makes OTLP export failures visible in the GitHub Actions “Observability” step summary by reading locally persisted export error count and JSONL failure details and rendering them in the run summary.
Changes:
- Add OTLP export error count + warning line to the observability step summary output.
- Parse and render per-endpoint OTLP export failure details from a JSONL file (defensively).
- Extend Vitest coverage to assert OTLP error count/detail rendering and absent-files behavior.
Show a summary per file
| File | Description |
|---|---|
| actions/setup/js/generate_observability_summary.cjs | Reads OTLP export error count/details from /tmp/gh-aw and surfaces them in the Observability step summary. |
| actions/setup/js/generate_observability_summary.test.cjs | Adds assertions and fixtures to validate OTLP export error count/warning/details rendering, including zero-count when files are absent. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
Comment on lines
+166
to
+170
| if (data.otlpExportErrorDetails.length > 0) { | ||
| lines.push("- **otlp export failure details**:"); | ||
| for (const detail of data.otlpExportErrorDetails) { | ||
| lines.push(` - ${detail}`); | ||
| } |
Comment on lines
+57
to
+61
| fs.writeFileSync("/tmp/gh-aw/otlp-export-errors.count", "2\n"); | ||
| fs.writeFileSync( | ||
| "/tmp/gh-aw/otlp-export-errors.jsonl", | ||
| [JSON.stringify({ host: "collector-a.example.com:4318", status: 401, reason: "Unauthorized" }), JSON.stringify({ host: "collector-b.example.com:4318", reason: "upstream timeout" })].join("\n") | ||
| ); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OTLP export failures were already persisted locally but not shown in the GitHub Actions Observability summary, creating a false “healthy” signal when backend export was broken. This change makes export health explicit in the run page summary, even when the conclusion span cannot be delivered.
Observability summary now reports OTLP export health
generate_observability_summary.cjsnow reads:/tmp/gh-aw/otlp-export-errors.count/tmp/gh-aw/otlp-export-errors.jsonlotlp export errorscounthost, optionalstatus,reason)Failure details are parsed defensively
Focused test coverage updated
generate_observability_summary.test.cjsnow asserts: