Forum Discussion
Solved
Send to analytics data collector errors
I have two playbooks that collect logs in JSON format from a 3rd party API (Proofpoint TAP and Cisco AMP for endpoints). When I run the playbooks I can see that each one gets data from the third par...
Ofer and I discussed offline. The solution is detailed here:
One thing I would note, for the Proofpoint playbook, even after adding the step to parse the JSON I would get errors like “expected integer but got a number” or “expected string and got null.” The fix was to go back into the schema in the step and find places where the value was integer and set it to allow an integeor or a number. Same thing for string, allow string or null.
Ofer and I discussed offline. The solution is detailed here:
One thing I would note, for the Proofpoint playbook, even after adding the step to parse the JSON I would get errors like “expected integer but got a number” or “expected string and got null.” The fix was to go back into the schema in the step and find places where the value was integer and set it to allow an integeor or a number. Same thing for string, allow string or null.
andrew_bryant: Thank you!