[Feature]: Java Workflow Insight plugin follow-up work
Maintainer antworten meist innerhalb von 1 Tag
@wangyb-A arbeitet bereits daran.
Seit 02.9.2026.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
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-pluginMaven module. - Support schema version
1.0of the Workflow Insight record. - Support
ON_COMPLETE,ON_FAILURE, andON_CHANGEemission 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
operationsarray. - 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
RUNNINGrecords. - 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
- Java implementation:
PR #661 - Follow-up work:
Issue #679 - Conformance requirements:
Conformance PR #73 - JavaScript reference:
Workflow Insight package
Is this a breaking change?
No.
Does this require an RFC?
No.
- Vorherrschende Sprache
- Java
- Sterne
- 28
- Forks
- 16
- Ø Merge
- 1 T. 23 Std.
- Gemergte PRs (30 T.)
- 68
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus aws/aws-durable-execution-sdk-java
-
documentation pkg:sdk
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 88/100
aws/aws-durable-execution-sdk-java#645 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
aws/aws-durable-execution-sdk-java#300 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Feature]: Add invocation-owned executor isolationEvtl. vergeben @zhongkechen hat das vor 33 Tagen übernommen. Offenenhancement needs-triage
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 1/100
aws/aws-durable-execution-sdk-java#840 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug needs-triage
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
aws/aws-durable-execution-sdk-java#839 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug]: Enforce invocation deadlines while awaiting owner cleanupEvtl. vergeben @zhongkechen hat das vor 33 Tagen übernommen. Offenbug needs-triage
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 1/100
aws/aws-durable-execution-sdk-java#838 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in aws/aws-durable-execution-sdk-java
Ähnliche Issues
-
bug web-server
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
jooby-project/jooby#4035 ·
Maintainer antworten meist innerhalb von 1 Tag
-
L: javascript
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
dependabot/dependabot-core#16744 ·
Maintainer antworten meist innerhalb von 1 Tag
-
intake mcp-intake needs-human-review priority:high type:bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
Ikalus1988/MisakaNet#3987 · 3 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
quarkiverse/quarkus-google-cloud-services#1187 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 82/100
locationtech/jts#1250 ·