-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Standardization] KaaS Logging/Monitoring/Tracing #418
[Standardization] KaaS Logging/Monitoring/Tracing #418
Comments
Notes from prioritization meeting 06-10-23:
|
monitoring:I investigated how gardener handles monitoring. The federated monitoring could also be a suitable approach for monitoring SCS k8s clusters.
logging(draft):I also investigated how gardener handles logging. It very much depends on the use of certain tools. In addition, Kubernetes does not offer “logging at cluster level” see. It is therefore recommended to use one of the various common approaches for “logging at cluster level” |
Note that scs-0403-v1-csp-kaas-observability-stack also covers part of the subject of this topic. In contrast to gardener's approach, it relies on the use of Thanos. |
This issue was created to provide a discussion ground for possible future standards. It is derived from #181 and on of the points not assigned any issue yet.
The following topics/ideas should be discussed and maybe extended:
Definition of Done:
The text was updated successfully, but these errors were encountered: