Forum Discussion
vyasyash
9 years agoNew Contributor III
Hello Eguo,
Thanks for suggesting the way to capture the input/output document of snaps.
I’m new to SnapLogic world, and come from traditional ESB background. Wanted to understand if SnapLogic provides any out of the box feature to capture the input & output document for auditing and logging purpose (both in case of synchronous and async scenario). In production scenarios input/out payload will come handy to conduct RCA of the failed interface pipeline.
Thanks in advance.
Best,
Yashu Vyas
eguo
9 years agoFormer Employee
@vyasyash, welcome to the post-ESB paradigm!
No there is no out of box feature to persist messages like in traditional ESB, hence created the approach in this post to enable troubleshooting activities.
Benefits of this approach:
- It avoids introducing new I/O endpoints into the pipeline. As a result, the pipeline has less state to manage in the runtime.
- You could use Pipeline Monitoring API to consume the captured information to satisfy certain use cases.
Limitations:
- Only the last rolling hundred sub-pipeline’s runtime logs will be kept by SL platform therefore visible in the dashboard and accessible via the Pipeline Monitoring API.
- A runtime log will be kept in SL platform for 90 days.
- Can not enable the reuse in the pipeExec snap.
Eddy