Skip to content

[Test Case] - Verify logs of observability components #9634

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
suleymanakbas91 opened this issue Oct 6, 2020 · 7 comments
Closed

[Test Case] - Verify logs of observability components #9634

suleymanakbas91 opened this issue Oct 6, 2020 · 7 comments
Labels
area/monitoring Issues or PRs related to the monitoring module (deprecated) lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. test-case

Comments

@suleymanakbas91
Copy link
Contributor

suleymanakbas91 commented Oct 6, 2020

Summary

The purpose of the test is to assure that there are no unexpected error logs in our components indicating potentially real issues

Automation Steps
Have a new test case that verifies all logs of our components and asserts on new error messages. There must be a way to whitelist errors.
The test case should be integrated into all typical test suites without having the assertion activated (only printing the results). At a later stage, we will activate the assertion.
There should be a new pre-submit job that is triggered only for our components which will assert

Manual Test Cases

kubectl logs --tail=-1 -l app=grafana -n kyma-system -c grafana | grep -v 'lvl=info'
kubectl logs --tail=-1 -l app=grafana -n kyma-system -c grafana-sc-dashboard-watcher
kubectl logs --tail=-1 -l app=grafana -n kyma-system -c grafana-sc-datasources-watcher
kubectl -n kyma-system logs -l app=prometheus -c prometheus --tail -1 | grep -v 'level=info'
kubectl -n kyma-system logs -l app=prometheus -c config-reloader --tail -1 | grep -v 'level=info'
kubectl -n kyma-system logs -l app=prometheus-node-exporter --tail -1 | grep -v 'level=info'
kubectl -n kyma-system logs -l app=monitoring-operator --tail -1 | grep -v 'level=info'
kubectl -n kyma-system logs -l app.kubernetes.io/name=alertmanager -c alertmanager --tail -1 | grep -v 'level=info'
kubectl -n kyma-system logs -l app.kubernetes.io/name=kube-state-metrics --tail -1
@suleymanakbas91 suleymanakbas91 added area/monitoring Issues or PRs related to the monitoring module (deprecated) test-case labels Oct 6, 2020
@suleymanakbas91 suleymanakbas91 changed the title [Test case] - Check the Prometheus targets and alerts [Test Case] - Check the Prometheus targets and alerts Oct 7, 2020
@ghost
Copy link

ghost commented May 13, 2021

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the stale label May 13, 2021
@a-thaler a-thaler removed the stale label May 17, 2021
@ghost
Copy link

ghost commented Jul 16, 2021

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the stale label Jul 16, 2021
@a-thaler a-thaler removed the stale label Jul 19, 2021
@ghost
Copy link

ghost commented Sep 25, 2021

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the stale label Sep 25, 2021
@ghost
Copy link

ghost commented Nov 26, 2021

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the stale label Nov 26, 2021
@ghost
Copy link

ghost commented Dec 3, 2021

This issue has been automatically closed due to the lack of recent activity.

@ghost ghost closed this as completed Dec 3, 2021
@a-thaler a-thaler reopened this Dec 3, 2021
@a-thaler a-thaler removed the stale label Dec 3, 2021
@ghost
Copy link

ghost commented Feb 1, 2022

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the stale label Feb 1, 2022
@a-thaler a-thaler removed the stale label Feb 2, 2022
@a-thaler a-thaler added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Apr 11, 2022
@a-thaler a-thaler changed the title [Test Case] - Check the Prometheus targets and alerts [Test Case] - Verify logs of observability components Apr 26, 2022
@a-thaler
Copy link
Contributor

With the removal of the monitoring component, this test case is obsolete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/monitoring Issues or PRs related to the monitoring module (deprecated) lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. test-case
Projects
None yet
Development

No branches or pull requests

3 participants