Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

event informations #33

Open
pasztorl opened this issue Mar 2, 2023 · 1 comment
Open

event informations #33

pasztorl opened this issue Mar 2, 2023 · 1 comment

Comments

@pasztorl
Copy link

pasztorl commented Mar 2, 2023

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?

@aantn
Copy link
Collaborator

aantn commented Mar 7, 2023

Hey, thanks for the feedback.

You can send the full information via the cloudevents handler. (The source code has full reference for what's sent.)

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.)

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

No branches or pull requests

2 participants