Skip to content

GKE Multitenant Blueprint - logging configuration #1639

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

Closed
olliefr opened this issue Aug 31, 2023 · 1 comment · Fixed by #1638
Closed

GKE Multitenant Blueprint - logging configuration #1639

olliefr opened this issue Aug 31, 2023 · 1 comment · Fixed by #1638

Comments

@olliefr
Copy link
Collaborator

olliefr commented Aug 31, 2023

Hey,

While working on #1638 I had noticed that the README for GKE Multitenant Blueprint states:

- Logging and monitoring configured to use Cloud Operations for system components and user workloads.

My interpretation of this is such that both SYSTEM_COMPONENTS and WORKLOADS logs are being ingested as per LoggingComponentConfig.

The examples in the blueprint README do not include any logging configuration so it falls back to the default value, which is defined to be system logs only:

logging_config = optional(list(string), ["SYSTEM_COMPONENTS"])

I think this is a divergence from what's stated in the README and either the README or the default value must be corrected.

I'm interested to know what, in your opinion, the answer should be so that I can update #1638 🙃

Default logging in Cloud Console vs gke-cluster-standard

I think this might be a consequence of a bigger point although I am not sure if it warrants a separate issue - in Cloud Console, pre-selected values for logging configuration are system logs and workloads, indeed.

In gke-cluster-standard as it stands today, the default value is system logs only.

I'm not sure if this divergence is intentional.

@olliefr
Copy link
Collaborator Author

olliefr commented Aug 31, 2023

While working on updating the example for using the new logging_config interface in #1638, I'd updated the example to also include WORKLOADS in the logs source.

Thus, once #1638 is merged there is going to be no discrepancy between the README and the code.

Commit: fe13131

@olliefr olliefr linked a pull request Aug 31, 2023 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant