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

GKE & Cloud Logging usability #6531

Open
Blasterdick opened this issue Sep 29, 2021 · 0 comments
Open

GKE & Cloud Logging usability #6531

Blasterdick opened this issue Sep 29, 2021 · 0 comments
Assignees
Labels
area/platform issues related to the platform autoteam frozen Not being actively worked on kubernetes team/platform-hold team/platform-move type/enhancement New feature or request

Comments

@Blasterdick
Copy link

Blasterdick commented Sep 29, 2021

Just started Airbyte v0.29.22 in minikube, and looking forward to deploy it to GKE, but have a concern regarding logging.

To lookup for the application logs, I'm using Cloud Logging. GKE consumes JSONL lines from the pod containers and pushes them into the Cloud Logging. Is there a way to make cluster working components to print stdout/stderr in JSONL? That would make use of the severity field and so on, making working with Airbyte logs on GKE much more comfortable.

Thanks in advance.

Can be useful:

[1] https://cloud.google.com/community/tutorials/kubernetes-engine-customize-fluentbit
[2] https://docs.fluentbit.io/manual/installation/kubernetes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/platform issues related to the platform autoteam frozen Not being actively worked on kubernetes team/platform-hold team/platform-move type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

7 participants