Skip to content

[Requirement]: Telemetry record for a retry, a repeated step name, and opted-in operation results #159

Open

Description

@hln33

Operation / suite

New operation (describe below): telemetry

Behavior to cover

Three cases:

  1. A step that fails once and then succeeds under a retry policy.
  2. Two steps with the same name.
  3. A step with operation-result capture opted in.

Why it matters

Retry changes count and the duration fields. Repeated names exercise operationsByName keying. An opted-in result is currently accepted with any value (#153), including the Python serializer form {"t": ..., "v": ...}.

Expected cross-SDK behavior

The same count, the same operationsByName keying, and the result serialized in one agreed format.

Follow-up from #144. Review: #144 (review). Tracking issue: #63.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions