Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Feature]: Java Workflow Insight plugin follow-up work

未关闭
  • 哪里不对？
#679 4 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@wangyb-A 已经在做这个了。

开始于 2026年9月2日。

评估

这个 Issue 还没有评估数据。

描述

enhancement parity pkg:sdk
What would you like?

Add a Workflow Insight plugin to the AWS Lambda Durable Execution SDK for Java.

The plugin should emit a structured summary of each durable execution, including
execution status, timing, input/output, errors, and operation details. It should
follow the JavaScript Workflow Insight contract where practical while accounting
for Java-specific threading, serialization, and plugin lifecycle behavior.

Why?

Customers need an easier way to inspect and analyze durable workflows without
reconstructing execution state from raw Lambda logs and execution history.

Workflow Insight records enable:

  • Execution monitoring and troubleshooting
  • Workflow latency and failure analysis
  • Operation-level visibility
  • Querying records through CloudWatch Logs, S3, and analytics tools
  • Consistent observability across JavaScript, Python, and Java SDKs
Initial scope
  • Add a publishable insight-plugin Maven module.
  • Support schema version 1.0 of the Workflow Insight record.
  • Support ON_COMPLETE, ON_FAILURE, and ON_CHANGE emission modes.
  • Support deterministic per-execution sampling.
  • Support top-level and full-tree operation detail.
  • Support input/output transforms, operation result transforms, filtering, and
    error controls.
  • Support record-size limits and deterministic truncation.
  • Isolate plugin and exporter failures from durable execution.
  • Publish the plugin to Maven Central and attach it to GitHub releases.
Acceptance criteria
  • Java plugin hooks expose the execution and operation data required by the
    record contract.
  • Workflow Insight module builds as part of the Maven reactor.
  • Records include execution metadata, operation summaries, errors, attempts,
    and opted-in results.
  • S3 emits the canonical operations array.
  • Lambda and CloudWatch Logs emit operationsByName.
  • Sampling, content controls, filtering, truncation, and exporter isolation
    have unit coverage.
  • S3 Workflow Insight conformance passes all applicable requirements.
  • CloudWatch Workflow Insight conformance passes all applicable requirements.
  • Release automation publishes the new Maven artifact.
  • Public preview APIs use @Experimental.
  • includeErrors(false) suppresses execution and operation errors.
  • Plugin Throwables do not disrupt durable execution.
  • Add an ADR documenting the record contract, lifecycle, sampling,
    truncation, content-transform, and exporter-ordering decisions.
  • Add customer-facing installation, IAM, configuration, schema, and
    troubleshooting documentation.
  • Add automated cloud integration coverage for both S3 and CloudWatch.
  • Complete final human review and merge the implementation PR.
Design constraints
  • Plugin failures must never change the durable execution result.
  • Remote exporter I/O must not block SDK checkpoint coordination.
  • Memory use must remain bounded across suspended and resumed executions.
  • Terminal records must not be overwritten by delayed RUNNING records.
  • Sensitive input, output, and error content must be configurable.
  • Sampling decisions and record behavior should remain aligned across SDKs.
  • Breaking record-contract changes require a schema-version change.
Follow-up work

Check the comments

Links
Is this a breaking change?

No.

Does this require an RFC?

No.

主要语言
Java
星标
28
派生
14
平均合并
2 天 13 小时
30 天内合并 PR
47

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

aws/aws-durable-execution-sdk-java 的其他 Issue

查看 aws/aws-durable-execution-sdk-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。