Skip to content
This repository has been archived by the owner on Aug 31, 2022. It is now read-only.

Only log out to the sink #169

Open
Shaybs opened this issue Nov 30, 2021 · 1 comment
Open

Only log out to the sink #169

Shaybs opened this issue Nov 30, 2021 · 1 comment

Comments

@Shaybs
Copy link

Shaybs commented Nov 30, 2021

Hi,
It seems that the K8s Events Exporter is logging out at the DEBUG level. Whereas we'd only like the logs to stdout.

Current:

2021-11-30T16:38:36Z DBG app/pkg/kube/watcher.go:66 > Received event involvedObject=alertmanager-6f765fff5f-dkkdw msg="Back-off restarting failed container" namespace=default reason=BackOff
2021-11-30T16:38:36Z DBG app/pkg/exporter/channel_registry.go:56 > sending event to sink event="Back-off restarting failed container" sink=dump
{"metadata":{"name":"alertmanager-6f765fff5f-dkkdw.16bbef1fd46955ec","namespace":"default","uid":"ec30fbd1-c9ca-4011-9a6d-b3c20996ff73","resourceVersion":"56920823","creationTimestamp":"2021-11-29T06:03:29Z"},"reason":"BackOff","message":"Back-off restarting failed container","source":{"component":"kubelet","host":"ip-10-10-130-237.eu-west-1.compute.internal"},"firstTimestamp":"2021-11-29T06:03:29Z","lastTimestamp":"2021-11-30T16:38:36Z","count":9783,"type":"Warning","eventTime":null,"reportingComponent":"","reportingInstance":"","involvedObject":{"kind":"Pod","namespace":"default","name":"alertmanager-6f765fff5f-dkkdw","uid":"0cfca081-698e-47c4-8cb4-9b9d35ea8bba","apiVersion":"v1","resourceVersion":"56210742","fieldPath":"spec.containers{alertmanager}","labels":{"app":"alertmanager","coralbay.tv/container-type":"monitoring","coralbay.tv/stack":"coral-stats","coralbay.tv/system":"dev-demo2","pod-template-hash":"6f765fff5f"}}}

After turning off dubug we'd expect to get only the stdout:

{"metadata":{"name":"alertmanager-6f765fff5f-dkkdw.16bbef1fd46955ec","namespace":"default","uid":"ec30fbd1-c9ca-4011-9a6d-b3c20996ff73","resourceVersion":"56920823","creationTimestamp":"2021-11-29T06:03:29Z"},"reason":"BackOff","message":"Back-off restarting failed container","source":{"component":"kubelet","host":"ip-10-10-130-237.eu-west-1.compute.internal"},"firstTimestamp":"2021-11-29T06:03:29Z","lastTimestamp":"2021-11-30T16:38:36Z","count":9783,"type":"Warning","eventTime":null,"reportingComponent":"","reportingInstance":"","involvedObject":{"kind":"Pod","namespace":"default","name":"alertmanager-6f765fff5f-dkkdw","uid":"0cfca081-698e-47c4-8cb4-9b9d35ea8bba","apiVersion":"v1","resourceVersion":"56210742","fieldPath":"spec.containers{alertmanager}","labels":{"app":"alertmanager","coralbay.tv/container-type":"monitoring","coralbay.tv/stack":"coral-stats","coralbay.tv/system":"dev-demo2","pod-template-hash":"6f765fff5f"}}}

Is that possible? COuld anyone elaborate on how to do that?

@Shaybs
Copy link
Author

Shaybs commented Nov 30, 2021

The current configuration is exactly as recommended by Mustafa Akin in deploy section of this repo, I am just wondering how the config can be changed to stop the DBG logs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant