Skip to content

Document aspire export zip archive contents in monitoring.md #16719

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Copilot wants to merge 3 commits into
base: main
Choose a base branch
from
+8 −1
Open

Document aspire export zip archive contents in monitoring.md #16719

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9948f35
Update monitoring.md with aspire export file contents documentation
Copilot May 4, 2026
7991aab
Potential fix for pull request finding
JamesNK May 4, 2026
fe46f47
Apply suggestion from @JamesNK
JamesNK May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .agents/skills/aspire/references/monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,9 +47,16 @@ Use this command when you need a portable handoff artifact for deeper analysis o
aspire export [resource]
```

Keep this point in mind:
Keep these points in mind:

- Use `aspire export` when you need a sharable bundle of telemetry and resource state.
- `[resource]` is optional. Include it to filter the export to a single resource; omit it to export all resources.
- The output is a zip archive (default name `aspire-export-<timestamp>.zip`) containing up to four directories:
- `resources/` — one JSON file per resource with resource details (name, type, state, endpoints, environment variables, etc.).
- `consolelogs/` — one plain-text file per resource with raw console output lines.
- `structuredlogs/` — one JSON file per resource with structured log entries in OTLP format.
- `traces/` — one JSON file per resource with distributed traces and spans in OTLP format.
- When extracting the export for analysis, look at `resources/` first for an overview, then drill into `consolelogs/`, `structuredlogs/` and `traces/` for detailed diagnostics.

## Dashboard Links

Expand Down
Loading