Is your feature request related to a problem? Please describe. There's already support to capture last log line and customize it, but if log message too long slack will trim it, My experience I set only for last 10 log but still get trim, and quote disappeared at last make message not block by quote

Describe the solution you'd like Maybe we can make that still send full log but via file instead of quote the message? Or only send real last log, instead of first last log that get trimmed

Is your feature request related to a problem? Please describe. We always receive the notification when the pod is in status "Podinitializing", this happens all day, but is a false positive.

Describe the solution you'd like I would like to filter the "Reason" field on the message, to send to slack just the "CrashLoopback", and another errors, not all the errors.

Describe the bug When I delete a pod (or an object containing pods, i.e. deployment) normally (also tested via argocd) I receive an alert about a pod crash:

 kwatch detected a crash in pod
There is an issue with container in a pod!
Name
rex2-c8f75f688-nxczd
Container
tools
Namespace
myns
Reason
Error
Events
...
[2022-01-20 20:36:45 +0000 UTC] Created Created container rex2
[2022-01-20 20:36:45 +0000 UTC] Started Started container rex2
...
[2022-01-20 20:38:34 +0000 UTC] Killing Stopping container rex2
...

 Logs
unable to retrieve container logs for docker://c733494c9012466a9d98cf6bacf629127f3741d6d23c18e48c71d3237466965d
kwatch

This isn't a crash but a normal container termination, I should not be getting alerts

To Reproduce Steps to reproduce the behavior:

• run kwatch
• delete some pod

Expected behavior

I should not receive alerts on cleanly terminated pods, only on crashes

Actual behavior Getting a crash alert

Version/Commit v0.3.0

Is your feature request related to a problem? Please describe. https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook

Describe the solution you'd like Need to use it to MS Teams to use it to my company

thank you

Bumps k8s.io/apimachinery from 0.24.1 to 0.24.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps k8s.io/api from 0.24.1 to 0.24.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps k8s.io/apimachinery from 0.24.0 to 0.24.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps k8s.io/api from 0.24.0 to 0.24.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps k8s.io/apimachinery from 0.23.6 to 0.24.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps k8s.io/api from 0.23.6 to 0.24.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps k8s.io/api from 0.23.5 to 0.23.6.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

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 of this except tricky bash script and setup complex monitoring stacks like grafana and so on

Describe the solution you'd like I think we just need a simplest feature for kwatch right, like when pvc touch 80% or higher send notification to third party and so on whatever, simple problem doesn't need complex installation/solution

I am running in k8s built on a physical machine. When I create it according to the readme, the pod cannot run normally

[[email protected] kwatch]# kubectl get pod,cm -n kwatch -o wide
NAME                          READY   STATUS             RESTARTS   AGE   IP             NODE    NOMINATED NODE   READINESS GATES
pod/kwatch-6d8646995d-485qt   0/1     CrashLoopBackOff   8          24m   10.244.10.82   node4   <none>           <none>

NAME               DATA   AGE
configmap/kwatch   1      29m
[[email protected] kwatch]# 

I didn't make any changes to deploy.yaml file I only changed config.yaml file and received alerts using Telegram Below is my config.yaml file

apiVersion: v1
kind: Namespace
metadata:
  name: kwatch
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: kwatch
  namespace: kwatch
data:
  config.yaml: |
    ignoreFailedGracefulShutdown: true
    alert:
      telegram:
          token: 5207405246:AAE6_pOIjC065T9agYg9xsePrfwZR8yuggU
          chatId: 1732858888

The pod is restarting continuously, the log is as follows:

[[email protected] kwatch]# kubectl logs -f kwatch-6d8646995d-485qt -n kwatch
time="2022-03-29T11:37:02Z" level=info msg=":tada: [email protected] just started!"
time="2022-03-29T11:37:02Z" level=info msg="using config file: /config/config.yaml"
panic: interface conversion: interface {} is int, not string

goroutine 1 [running]:
github.com/abahmed/kwatch/util.GetProviders()
	/build/util/util.go:135 +0x12c5
main.main()
	/build/main.go:36 +0x1f3
[[email protected] kwatch]# 

Event information is:

Events:
  Type     Reason     Age                 From               Message
  ----     ------     ----                ----               -------
  Normal   Scheduled  25m                 default-scheduler  Successfully assigned kwatch/kwatch-6d8646995d-485qt to node4
  Normal   Pulled     25m                 kubelet            Successfully pulled image "ghcr.io/abahmed/kwatch:v0.5.0" in 2.161757876s
  Normal   Pulled     25m                 kubelet            Successfully pulled image "ghcr.io/abahmed/kwatch:v0.5.0" in 2.517168612s
  Normal   Pulled     24m                 kubelet            Successfully pulled image "ghcr.io/abahmed/kwatch:v0.5.0" in 2.838614125s
  Normal   Created    24m (x4 over 25m)   kubelet            Created container kwatch
  Normal   Pulled     24m                 kubelet            Successfully pulled image "ghcr.io/abahmed/kwatch:v0.5.0" in 7.035699291s
  Normal   Started    24m (x4 over 25m)   kubelet            Started container kwatch
  Normal   Pulling    23m (x5 over 25m)   kubelet            Pulling image "ghcr.io/abahmed/kwatch:v0.5.0"
  Warning  BackOff    7s (x101 over 25m)  kubelet            Back-off restarting failed container

My kubernetes cluster version is v1.19.4. OS version is CentOS Linux release 7.6.1810 (Core) I don't know what's causing it please give me an answer, thanks

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
    alert:
      telegram:
          token: XXX
          chatId: -YYY

Error in pod logs:

level=error msg="failed to send event with Telegram: Post "https://api.telegram.org/botXXX/sendMessage": x509: certificate signed by unknown authority"

Expected behavior Should get kwatch notification to my Telegram channel.

Version/Commit A version or commit of kwatch: 0.5.0 I'm run kwatch in k8s (1.17), as described in manual.

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 down
[2022-03-24 14:53:55 +0000 UTC] Killing Stopping container kube-proxy

Describe the solution you'd like I would like those to have the option for those messages to be ignored

Is your feature request related to a problem? Please describe. I would like to see a more compact notifications (at least on Slack), as the current format takes up a lot of screen space and I wish the information would be more dense and less verbose.

Describe the solution you'd like Example what it looks currently (screenshot is from the readme):

Translating to text:

Pod Crash

There is an issue with your pod!

Name                             Container
mytest                           nginx

Namespace                        Reason
default                          ErrImagePull

Events
…
…
…

Logs:
…

It would be great if there was an option to have a condensed format, example:

kwatch: Pod Crash: default/mytest:nginx: ErrImagePull

Further it would be great if both "Events" and "Logs" can be tuned to only show the last n lines, ranging from 0 to Inf or so.

With n being 1:

kwatch: Pod Crash: default/mytest:nginx: ErrImagePull

Events:
<last line>

Logs:
<last line>

If either the last lines for Events/Logs is 0, it shouldn't be displayed at all.

(well, maxRecentLogLines is already there for "Logs", just wanted to mention it in regards for "Events")

WDYT? Thank you for considering 🙏🏼

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.

Actual behavior When I checked the pod logs, it gives the following error:

time="2022-02-23T13:23:01Z" level=error msg="failed to send msg with Microsoft Teams: call to teams alert returned status code 400: Bad payload received by generic incoming webhook."

Version/Commit 0.4.0