Skip to content

test: measure Collector queue saturation and in-flight restart - #4

Draft
dinakarjs wants to merge 1 commit into
test/collector-fault-harnessfrom
test/collector-queues-20261025
Draft

dinakarjs wants to merge 1 commit into
test/collector-fault-harnessfrom
test/collector-queues-20261025

Conversation

@dinakarjs

Copy link
Copy Markdown
Owner

Add a bounded experiment against the existing pinned official Collector 0.163.2 binary. A receiver barrier holds one export before commit while a second request occupies the remaining memory-queue capacity. Check overflow refusal, then separately SIGKILL at that boundary and measure recovery using a fresh request. SQLite retains attempted/committed identities; summaries distinguish submitted, HTTP-accepted and committed events.

Stacked follow-up to agentrust-io#100 at 2714186. This fork PR isolates the follow-up pending parent adoption. Coordinate the shared workflow/README changes with the fidelity companion when rebasing.

Validation: three accounting tests pass; Python compilation, focused Ruff and actionlint pass. The real pinned Collector saturation case returned 200/200/503 and committed the first two identities. A subsequent Collector startup failed with the known sandbox failed to register process metrics: process does not exist error. The complete in-flight restart case has not passed locally and remains a required hosted experiment before merge; no full-run success is claimed.

Direct synthetic OTLP requests exercise the Collector, not SDK retry behavior. The queue is in memory, the receiver deliberately discards the interrupted request, and accepted-but-uncommitted records establish only this experiment's observation. No persistent-queue, power-loss, production durability or exactly-once claim. AI-assisted with Codex; DCO signed.

Signed-off-by: Srinivasa Consultants <78673153+dinakarjs@users.noreply.github.com>
@github-actions

github-actions Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

🟡 Contributor Check: MEDIUM

Check Result
Profile MEDIUM
Credential LOW
Overall MEDIUM

Automated check by AgenTrust Contributor Check.

@github-actions github-actions Bot added the needs-review:MEDIUM Contributor check flagged MEDIUM risk label Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-review:MEDIUM Contributor check flagged MEDIUM risk

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant