JSON reading of audit log

Follow

Donald Graham

• June 19, 2019 18:54

According to the D3SA documentation in regards to the audit log

The log is output in JSON format which allows for post-processing and further analysis. For example, it can be read by the JSON Data node.

The first issue I ran into was the need to set the CoerceData property to "On Conflict"

Now I am getting another error

Error occurred while processing parsed data and sending to the nodes outputs: Reserved character (:) on metadata field (8), name: arguments.saveOptions.object:!tenant:defaultTenant~workspace:502fb286-2863-47e2-bc4e-767921764155~edit-session:9821058c-0e7e-4fa3-b5a1-54c15481a1d4~graph:523f328e-8439-4a5d-8c5d-a3778a625356.includeTargetWorkspaceInSearchPath, type: class java.lang.Boolean.

What needs to be done to allow the JSON Data node to work with this log file. 

0

• 

  Adrian Williams

  • June 26, 2019 13:18

  Have you tried setting the 'SubstituteInvalidCharacters' property (located in the Exception Behavior section of the properties panel) to True?

  0

  Comment actions Permalink
• 

  Donald Graham

  • June 27, 2019 17:48

  Yes Adrian. I have now set the SubstituteInvalidCharacters property and it does work thank you. I have also used the Input Raw data before you enlightened me. It doesn't work with the lae_webapp or server files but I use the input raw to get that data. 

  Thank you

  0

  Comment actions Permalink

Please sign in to leave a comment.