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
In this issue we agreed on the metrics we would like to graph on Grafana for the idle tests
This ticket is about gathering some inputs to define a workflow on how to collect & visualize the metrics.
This ticket is dependent on enabling the production of the falco-specific metrics like the kernel_event_rate
Once that is clear we should ask ourself how we transfer those data so that Grafana can graph them:
Another solution would be to write a custom script that reads from the file where falco saves the metrics /tmp/stats/falco_stats.jsonl and write back to a source that grafana can read (e.g. a MySQL database)
Another idea would be to check if the same metrics are also available at some endpoints so that Grafana can query them directly
Other inputs are really welcome!
The text was updated successfully, but these errors were encountered:
AntonioDiTuri
changed the title
Deep dive on Collect & visualise metrics workflow - FALCO
[ACTION] Deep dive on Collect & visualise metrics workflow - FALCO
Feb 6, 2024
In this issue we agreed on the metrics we would like to graph on Grafana for the idle tests
This ticket is about gathering some inputs to define a workflow on how to collect & visualize the metrics.
This ticket is dependent on enabling the production of the falco-specific metrics like the kernel_event_rate
Once that is clear we should ask ourself how we transfer those data so that Grafana can graph them:
One such a solution could be the https://github.com/falcosecurity/falco-exporter to export it to Prometheus and to read it from there
Another solution would be to write a custom script that reads from the file where falco saves the metrics /tmp/stats/falco_stats.jsonl and write back to a source that grafana can read (e.g. a MySQL database)
Another idea would be to check if the same metrics are also available at some endpoints so that Grafana can query them directly
Other inputs are really welcome!
The text was updated successfully, but these errors were encountered: