[Copilot]

• Policy: Extend the existing database guidance to RPC: don’t request a separate response-status attribute when status is captured only on failures and would duplicate error.type.
• Capture behavior: Preserve status attributes for instrumentation that captures both successful and failed operations, including failures whose status matches error.type. Keep status-based error classification and exception-type fallback unchanged.

[opentelemetry-pr-dashboard]

Pull request dashboard status

Merged · refreshed 2026-10-21 05:54 UTC

Status above doesn't look right?

• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.

[Copilot]

🟢 Approval recommended

The documentation-only changes clearly express the intended policy with no unresolved issues.

No open issues 🎉

What changed in this PR

Clarifies telemetry review guidance by extending the failure-only response-status policy to RPC.

Changes:

• Discourages redundant status attributes when failure codes already populate error.type.
• Preserves existing success/failure status capture, error classification, and exception-type fallback.

File	Description
.github/​instructions/​emitted-telemetry.instructions.md	Extends database guidance to RPC and clarifies instrumentation-level status retention.

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The focused documentation change matches the stated intent and has no identified actionable issues.

No open issues 🎉

_{Review effort: Balanced}