kwatch icon indicating copy to clipboard operation
kwatch copied to clipboard

:eyes: monitor & detect crashes in your Kubernetes(K8s) cluster instantly

Results 37 kwatch issues
Sort by recently updated
recently updated
newest added

Slack supports specifying channel in the message body so that the same webhook can send messages in different channels. It would be useful to have this feature.

Hi, one of the biggest annoyances I currently experience is that, running a lot of k8s CronJob resources, multiple times a day I get this > There is an issue...

**Describe the bug** With `kwatch` `v0.6.1` built using `go1.18.4`, running `kwatch` with no `config.yaml` in present directory, the `kwatch` application panics after issuing `WARN` about the missing config file: ```...

**Is your feature request related to a problem? Please describe.** PVC is great representation of disk in kubernetes, but one problem, no simple problem when we want to monitor usage...

enhancement

**Is your feature request related to a problem? Please describe.** I can only specify namespaces by name, not by a label **Describe the solution you'd like** entry in configmap that...

enhancement
WIP

**I am running in k8s built on a physical machine. When I create it according to the readme, the pod cannot run normally** ``` [root@node1 kwatch]# kubectl get pod,cm -n...

**Describe the bug** Although I set MS Teams channel webhook address in config.yaml file, I didn't get any notifications. **Expected behavior** Should get kwatch notification to my MS Teams channel....

**Is your feature request related to a problem? Please describe.** Any plan for matrix server room alert? **Describe the solution you'd like** Like other notifications I want to receive alerts...

**Describe the bug** Although I set Telegram channel webhook address in config.yaml file, I didn't get any notifications. **Actual behavior** My config: ``` data: config.yaml: | maxRecentLogLines: 10 ignoreFailedGracefulShutdown: true...

**Is your feature request related to a problem? Please describe.** I am getting errors from expected operations from cluster-autoscaler. ``` [2022-03-24 14:53:54 +0000 UTC] ScaleDown deleting pod for node scale...

enhancement