How to audit payload in pipeline?
Hi all,
I’m new to SnapLogic world with past working experience in traditional ESB products like IBM Message Broker, WebMethods ESB, TIBCO etc. Wanted to understand if SnapLogic provides any out of...
Forum Discussion
Thanks a lot CJ for your quick response.
I understood, as SnapLogic is more of a data streaming platform, the underlying philosophy doesn’t support capturing document data for auditing purpose.
In our project we’re prepping for a large implementation with around 700 + integration scenarios, which includes most of the business critical processes for the enterprise.
Depending on our typical requirements, if we still have to capture the incoming/outgoing document data, can you please suggest if for internal document processing SnapLogic follows any specific message(document) format from where document data can be accessed or using Copy snap is the only possible solution.
Regards,
Yashu Vyas
hi Yashu -
Even in other platforms that I have worked it is not recommended to log everything that comes your way. It just is a waste of space and resources. There are usually 3 levels of logging - info, warn, error
What I would recommend is to have a debug parameter and if the value equals Y then do the logging like CJ mentioned at important steps.
Doing this debug parameter will ensure that you are not capturing these logs in production once you set them to N.
Hope that makes sense.
