-
Notifications
You must be signed in to change notification settings - Fork 336
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
KubeArmor Telemetry Monitoring and Dashboards #836
Comments
@daemon1024 I would love to work on this issue. |
Awesome! |
@daemon1024 I'm new to kubeArmor, This enhancement looks interesting to me, so I would love to be a LFX mentee for this project, So Do you have any idea? about some good issues that will help me in understanding about telemetry events with Logs and Alerts and make me better for this project. |
Hi @daemon1024 . Seems this issues is language agnostic. Its mainly observability. Am i Right? |
You could try working on issues labeled good-first-issue to get familiar with the code base. |
Thanks @rahulk789 for letting me know. |
Hi @daemon1024 could be assign me this issue |
Feature Request
KubeArmor emits a lot of telemetry events with Logs and Alerts. But consuming and making sense out of these telemetry events might be hard. There's a need for parsing these telemetry, generate relevant metrics, allow filtering the data and create graphs and visualise it i.e. create an entire dashboard which makes the kubearmor telemetry data easy to consume.
We recently added syslog support to relay service - kubearmor/kubearmor-relay-server#19.
We should now be able to directly feed the Relay stdout to Logstash or Fluentd to capture logs and further analyze and visualize it. But we need to verify it and check if any other changes are required to readily consume the data.
Describe the solution you'd like
Explore one of the following stacks
The text was updated successfully, but these errors were encountered: