Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

SDC log4j format for filebeat agent

We are monitoring our StreamSets Pipeline applications using ELK with filebeat agent reading the SDC log files I created a simple pipeline to test how filebeat will react to reading SDC logs and these are the errors filebeat is spitting out.

2020-05-05T15:46:13-04:00 ERR Error decoding JSON: json: cannot unmarshal number into Go value of type map[string]interface {} 2020-05-05T15:46:13-04:00 ERR Error decoding JSON: json: cannot unmarshal number into Go value of type map[string]interface {}

Does anyone know if SDC log works out of the box for filebeat or do I need to alter the sdc-log4j.properties file for the correct output? I am new to ELK/filebeat do I need to alter what it is interpreting?