Draft: kaas logging monitoring tracing #656
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g/Tracing" Signed-off-by: Toni Finger <[email protected]>
Signed-off-by: Toni Finger <[email protected]>
Signed-off-by: Toni Finger <[email protected]>
Signed-off-by: Toni Finger <[email protected]>
2 tasks
|
|
||
| SCS KaaS infrastructure monitoring SHOULD be used as a diagnostic tool to alert operators and end users to system-related issues by analyzing metrics. | ||
| Therefore, it includes the collection and visualization of the corresponding metrics. | ||
| Optionally, an alerting mechanism COULD also be standardized. |
There was a problem hiding this comment.
IMO, we also need alerting to be mandatory when we say:
SCS KaaS infrastructure monitoring SHOULD be used as a diagnostic tool to alert operators and end users...
|
|
||
| This concept SHALL define monitoring and logging in a federated structure. | ||
| Therefore, a monitoring and logging stack MUST be deployed on each k8s cluster. | ||
| A central monitoring can then fetch data from the clusters individual monitoring stacks. |
There was a problem hiding this comment.
I would suggest rephrasing this sentence something to like this:
A central monitoring system can then fetch data from the individual clusters' monitoring stacks to Grafana to visualize the collected metrics.
| #### Kubernetes Metric Server | ||
|
|
||
| Kubernetes provides a source for container resource metrics. | ||
| The main purpose of this source is to be used for Kubernetes' built-in auto-scaling [kubernetes-metrics-server][kubernetes-metrics-server-repo]. |
There was a problem hiding this comment.
kubernetes-metrics-server-repo is missing at the end of the file where other links are defined.
|
|
||
| #### Prometheus Operator | ||
|
|
||
| One of the most commonly used monitoring tools in connection with Kubernetes is Prometheus |
There was a problem hiding this comment.
Suggested change
| One of the most commonly used monitoring tools in connection with Kubernetes is Prometheus | |
| One of the most commonly used monitoring tools in connection with Kubernetes is Prometheus. |
Comment on lines
+64
to
+65
| Therefore, every k8s cluster CLOUD have a [prometheus-operator][prometheus-operator] deployed to all control plane clusters as an optional default. | ||
| The operator SHOULD at least be rolled out to all control plane nodes. |
There was a problem hiding this comment.
Can you please explain what has been meant by these two sentences? Something like that prometheus operator should/could be deployed at each k8s cluster and prometheus-node-exported should at least be rolled out on control plane nodes?
Co-authored-by: Michal Gubricky <[email protected]> Signed-off-by: tonifinger <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a decision record to configure monitoring for the SCS KaaS layer.
Addresses: SovereignCloudStack/issues#418