You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thanks for this great project. Showing what's happeing on a k8s cluster is very useful.
I started testing kubewatch, and I have two example about sent messages which is not so informative.
A Node in namespace `` has been Updated:
It would be great if we have more info about that.
A Event in namespace graylog has been Created:
graylog-mongodb-0.173e2cfeb153ed44
This is better, so I can see the event id.
kubectl get event graylog-mongodb-0.173e2cfeb153ed44 -n graylog
LAST SEEN TYPE REASON OBJECT MESSAGE
5m15s Warning Unhealthy pod/graylog-mongodb-0 Readiness probe failed: command "/opt/scripts/readinessprobe" timed out
I think it would be even better if kubewatch send the event contents. Or it is configurable and I'm missing something?
The text was updated successfully, but these errors were encountered:
If you want an easy to use solution that also formats the results, we also maintain Robusta which wraps KubeWatch and provides higher-level forwarding. (You can do full filtering on what is sent and template the messages.)
Hi,
First, thanks for this great project. Showing what's happeing on a k8s cluster is very useful.
I started testing kubewatch, and I have two example about sent messages which is not so informative.
A Node in namespace `` has been Updated:
It would be great if we have more info about that.
A Event in namespace graylog has been Created:
graylog-mongodb-0.173e2cfeb153ed44
This is better, so I can see the event id.
kubectl get event graylog-mongodb-0.173e2cfeb153ed44 -n graylog
LAST SEEN TYPE REASON OBJECT MESSAGE
5m15s Warning Unhealthy pod/graylog-mongodb-0 Readiness probe failed: command "/opt/scripts/readinessprobe" timed out
I think it would be even better if kubewatch send the event contents. Or it is configurable and I'm missing something?
The text was updated successfully, but these errors were encountered: