Closed TraianSandu closed 2 years ago
@TraianSandu, v2 uses new controller runtime and we changed to use structured logging. Do you have any hard dependencies on the old logging format? If it gets consumed by another application, how difficult would it be to migrate to the new format?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
/reopen
I get timeformat in epoch standard for alb pod logs, I wanted to have it in ISO 8601 standard
{"level":"info","ts":1719844438.041701,"msg":"version","GitVersion":"v2.4.1","GitCommit":"c4471defda10f8184173192b9f9df4e411ee5dac","BuildDate":"2022-03-16T16:10:01+0000"} {"level":"info","ts":1719844609.6857922,"logger":"controller-runtime.manager","msg":"starting metrics server","path":"/metrics"}
@Prasad1189: You can't reopen an issue/PR unless you authored it or you are a collaborator.
Hello!
We recently updated from old AWS ALB Ingress controller v1.1.9 to AWS Load Balancer Controller v.2.2.2. The upgrade went fine, but we noticed the time format inside logs changed : New alb-ingress version:
alb-ingress-controller-6449c486fc-hthwl alb-ingress-controller {"level":"info","ts":1628859653.6314578,"logger":"controllers.ingress","msg":"successfully deployed model","ingressGroup":"xxxx"}
Old alb-ingress version:
alb-ingress-controller-7c7b66bc4f-ll867 alb-ingress-controller I0813 12:29:08.517906 1 controller.go:236] kubebuilder/controller "level"=1 "msg"="Successfully Reconciled" "controller"="alb-ingress-controller" "request"={"Namespace":"xxxx","Name":"xxxx"}
Is there a way to change the way time is displayed inside ALB logs?Thank you!