Some log messages output from our 3scale API gateway pods running on OpenShift are being incorrectly classified at ERROR level when they are actually INFO messages.

Solution Verified - Updated -

Issue

  • Messages from apicast like:
2019/09/18 07:44:24 [debug] 16#16: *2 [lua] env.lua:86: fetch(): env: APICAST_VALIDATE_POLICY_CONFIGS = nil
2019/09/18 07:44:24 [debug] 16#16: *2 [lua] env.lua:86: fetch(): env: TEST_NGINX_BINARY = nil

were being logged to stderr, instead of stdout. This means that the 3scale messages, even if [info] like this one, are having the status set to error by fluentd.
Is this normal behaviour for 3Scale?
Is there away to modify 3Scale, so that [info] messages are not sent to stderr?

Environment

  • Red Hat 3scale API Management 2.X On-premises

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In