Open tobiscr opened 1 year ago
As long as the workload runs on GCP instance, the logs can be (or even are) automatically aggregated to GCP Stackdriver.
For logging strategy we have to find something that will met the requirements:
Prow components use logrus
. For our components AFAIK we use zap, but given that it requires a little bit of setting up I'd suggest https://github.com/rs/zerolog, or stay with logrus, as it's feature complete and more widely adopted.
This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
Isn't it a duplicate of #6303?
This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
This issue or PR has been automatically closed due to the lack of activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle stale
If you think that I work incorrectly, kindly raise an issue with the problem.
/close
@kyma-bot: Closing this issue.
There is no kind/
label present. Please add one by using the following command:
Available kinds:
deprecation
, bug
, chore
, feature
, flake
, cleanup
, missing-test
, failing-test
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.
This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten
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.
This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten
Description
Currently, each service or product of our CI/CD solution is logging decoupled form each other in different formats and even different locations.
For harmonising our log setup, we want to collect all log output in a standardised format and make them searchable in a centralised Cloud logging offering.
AC: