Change Details

Today the logging pipeline was spammed with DEBUG level logs from rdf-stream-updater / flink, we've reverted to a lesser log level (thank you @jijiki ) however it'd be good to investigate more on what's going on and how to prevent spam even in DEBUG. Additionally, logstash was spamming its own logs due to JSON parsing failure on the messages, e.g. {P17047} But I haven't been able to identify exactly what's failing in the parsing and what piece is responsible. cc @zpapierski @colewhite (not sure what other project tags to add) AC: * Valid json logs are produced regardless of a log level

Today the logging pipeline was spammed with DEBUG level logs from rdf-stream-updater / flink, we've reverted to a lesser log level (thank you @jijiki ) however it'd be good to investigate more on what's going on and how to prevent spam even in DEBUG. Additionally, logstash was spamming its own logs due to JSON parsing failure on the messages, e.g. {P17047} But I haven't been able to identify exactly what's failing in the parsing and what piece is responsible. cc @zpapierski @colewhite (not sure what other project tags to add) AC: * Valid json logs are produced regardless of a log level * exclude binary events from debug logs

Today the logging pipeline was spammed with DEBUG level logs from rdf-stream-updater / flink, we've reverted to a lesser log level (thank you @jijiki ) however it'd be good to investigate more on what's going on and how to prevent spam even in DEBUG. Additionally, logstash was spamming its own logs due to JSON parsing failure on the messages, e.g. {P17047} But I haven't been able to identify exactly what's failing in the parsing and what piece is responsible. cc @zpapierski @colewhite (not sure what other project tags to add) AC: * Valid json logs are produced regardless of a log level * exclude binary events from debug logs