[Feature]: Java Workflow Insight plugin follow-up work
Mantenedores costumam responder em até 1 dia
@wangyb-A já está trabalhando nisso.
Desde 2/9/2026.
Avaliação
Esta issue ainda não foi avaliada.
Descrição
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.
- Linguagem predominante
- Java
- Estrelas
- 28
- Forks
- 16
- Merge médio
- 2d 59min
- PRs com merge (30d)
- 62
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de aws/aws-durable-execution-sdk-java
-
bug pkg:conformance
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
aws/aws-durable-execution-sdk-java#844 ·
Mantenedores costumam responder em até 1 dia
-
documentation pkg:sdk
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 88/100
aws/aws-durable-execution-sdk-java#645 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
aws/aws-durable-execution-sdk-java#300 ·
Mantenedores costumam responder em até 1 dia
-
bug needs-triage pkg:sdk
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 35/100
aws/aws-durable-execution-sdk-java#859 ·
Mantenedores costumam responder em até 1 dia
-
bug needs-triage pkg:otel
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 48/100
aws/aws-durable-execution-sdk-java#858 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de aws/aws-durable-execution-sdk-java
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
AtlasOfLivingAustralia/species-lists#882 ·
Mantenedores costumam responder em até 1 dia
-
Type/Bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
ballerina-platform/ballerina-library#9458 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
winder/Universal-G-Code-Sender#3242 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
PCL-Community/PCL-CE#3767 ·
Mantenedores costumam responder em até 1 dia
-
#4 Implementar Ninja ServiceAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100