Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kong info, notice, inspect logs are all getting logged as error in GCP(google cloud platform) #13053

Closed
1 task done
sirishma opened this issue May 21, 2024 · 3 comments
Closed
1 task done
Labels
pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc... stale

Comments

@sirishma
Copy link

sirishma commented May 21, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Kong version ($ kong version)

2.5

Current Behavior

I have issues with logs, kong.log.notice, kong.log.info, kong.log.inspect are resulting in error logs in GCP.
SS_kong

Expected Behavior

No response

Steps To Reproduce

No response

Anything else?

I have tried setting SEVERITY to INFO manually, but to no avail. Any insights are appreciated.

@sirishma sirishma changed the title Kong info, debug, inspect logs are all getting logged as error in GCP(google cloud platform) Kong info, notice, inspect logs are all getting logged as error in GCP(google cloud platform) May 21, 2024
@nowNick
Copy link
Contributor

nowNick commented May 21, 2024

Hey @sirishma !

Thank you for opening up an issue! Could you share a bit more info about the Kong instance you are running? What plugins you have enabled? Is it traditional, hybrid or dbless mode?

Also please be aware that version 2.5 is no longer supported. You can try upgrading to the latest version 3.6, or if you'd like to stay on 2.x then go for 2.8 LTS version. For more info about our support policy please refer to: https://docs.konghq.com/gateway/latest/support-policy/

@nowNick nowNick added the pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc... label May 21, 2024
Copy link
Contributor

github-actions bot commented Jun 5, 2024

This issue is marked as stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale label Jun 5, 2024
Copy link
Contributor

Dear contributor,

We are automatically closing this issue because it has not seen any activity for three weeks.
We're sorry that your issue could not be resolved. If any new information comes up that could
help resolving it, please feel free to reopen it.

Your contribution is greatly appreciated!

Please have a look
our pledge to the community
for more information.

Sincerely,
Your Kong Gateway team

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc... stale
Projects
None yet
Development

No branches or pull requests

2 participants