Data360 Analyze

 View Only
  • 1.  JSON reading of audit log

    Employee
    Posted 06-19-2019 11:54

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    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. 



  • 2.  RE: JSON reading of audit log

    Employee
    Posted 06-26-2019 06:19

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



  • 3.  RE: JSON reading of audit log

    Employee
    Posted 06-27-2019 10:49

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    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