SLF4J errors ingested into Sumo Logic while collecting OKTA logs via SumoJanus package.

Problem:

I have installed Sumojanus package for collecting OKTA logs. I do see below error messages ingested into Sumo Logic along with OKTA logs

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Host: log-naor1 Name: Okta-Aquent Category: okta
2 03/29/2020
16:05:01.934
SLF4J: Defaulting to no-operation (NOP) logger implementation
Host: log-naor1 Name: Okta-Aquent Category: okta
3 03/29/2020
16:05:01.934
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Host: log-naor1 Name: Okta-Aquent Category: okta
4 03/29/2020
16:05:01.934
Found jar file: OktaCollector-1.0.1.jar
Host: log-naor1 Name: Okta-Aquent Category: okta
5 03/29/2020
16:05:01.934
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Resolution:

SumoJanus package ingests the STDOUT from the execution of the SumoJanus script. These errors are benign and you can create EXCLUDE/INCLUDE processing rules at source level to avoid ingestion of such error messages. Please read here more about processing rules.