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

[Standardization] KaaS Logging/Monitoring/Tracing #418

Open
2 tasks
cah-hbaum opened this issue Sep 12, 2023 · 3 comments · May be fixed by SovereignCloudStack/standards#656
Open
2 tasks

[Standardization] KaaS Logging/Monitoring/Tracing #418

cah-hbaum opened this issue Sep 12, 2023 · 3 comments · May be fixed by SovereignCloudStack/standards#656
Assignees
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling SCS is opinionated SCS has the courage to take decisions in its implementation choices to provide a clear focus SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10 standardization Standards & Certification

Comments

@cah-hbaum
Copy link

cah-hbaum commented Sep 12, 2023

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:

  • Logging
  • Monitoring
  • Tracing
  • make all these points optional (?)

Definition of Done:

  • Conclusions are reached about all discussion topics
  • A new issue for the creation of a standard (proposal) is created and linked
@cah-hbaum cah-hbaum added Container Issues or pull requests relevant for Team 2: Container Infra and Tooling SCS is standardized SCS is standardized standardization Standards & Certification SCS is opinionated SCS has the courage to take decisions in its implementation choices to provide a clear focus labels Sep 12, 2023
@jschoone jschoone modified the milestones: ClusterStack ClusterAddon: Observability, Cluster Stack ClusterAddon Sep 21, 2023
@cah-hbaum
Copy link
Author

cah-hbaum commented Oct 6, 2023

Notes from prioritization meeting 06-10-23:

  • solutions like gardener deploy stuff like logging / monitoring

  • what would be best-practice and what is probably required?

  • optional for a user, if he wants to deploy something like this in a cluster

  • can be more seen like a research issue

    • would probably create a DR

@cah-hbaum cah-hbaum moved this from Backlog to Doing in Sovereign Cloud Stack Jan 5, 2024
@cah-hbaum cah-hbaum self-assigned this Jan 5, 2024
@cah-hbaum cah-hbaum assigned tonifinger and unassigned cah-hbaum Mar 6, 2024
@tonifinger
Copy link

tonifinger commented Mar 27, 2024

monitoring:

I investigated how gardener handles monitoring.
In short: Gardener provides an integrated logging and monitoring stack that utilizes a number of prometheus-operators in a federated fashion. (see: https://gardener.cloud/docs/gardener/extensions/logging-and-monitoring/ )
A more detailed description of this concept can be found here: https://github.com/gardener/gardener/blob/master/docs/monitoring/README.md#prometheus

The federated monitoring could also be a suitable approach for monitoring SCS k8s clusters.
However, this depends on a certain combination of tools. The usage of those tools should not be mandatory, but could be an optional standard.
To conclude, I would consider the following aspects of gardener to be suitable for a definition of a standard:

  • (mandatory) federated approach
  • (optional) the usage of prometheus-operator on each cluster
  • (optional) maintenance of the monitoring stack

logging(draft):

I also investigated how gardener handles logging. It very much depends on the use of certain tools.
Compared to the monitoring setup, I would say that it cannot be used as a recommended reference implementation because it is too individual in its composition.
However, I would recommend providing a storage setup for log data, as Kubernetes itself cleans up its container log data after some time.

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”
Perhaps we can provide an optional standardized use of "logging agents" on each node to ensure that an SCS k8s cluster provides a logging mechanism.

@tonifinger
Copy link

tonifinger commented Apr 11, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling SCS is opinionated SCS has the courage to take decisions in its implementation choices to provide a clear focus SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10 standardization Standards & Certification
Projects
Status: Doing
Development

Successfully merging a pull request may close this issue.

4 participants