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

[Tracking] Gather metrics for idle Falco #34

Open
1 of 4 tasks
AntonioDiTuri opened this issue Jan 24, 2024 · 4 comments
Open
1 of 4 tasks

[Tracking] Gather metrics for idle Falco #34

AntonioDiTuri opened this issue Jan 24, 2024 · 4 comments

Comments

@AntonioDiTuri
Copy link
Contributor

AntonioDiTuri commented Jan 24, 2024

We decided to do first gather Falco idle metrics to validate our approach.
We gather metrics from k8s and kepler and we want to test those metrics for the falco project

Metrics

Check that the data have been loaded and think about a way to export those metrics.
There is no need for fancy export for the moment a csv or similar simple format would be fine

Benchmark test setup

@nikimanoledaki nikimanoledaki changed the title Gather metrics for idle Falco (Tracking) [Tracking] Gather metrics for idle Falco Jan 24, 2024
@nikimanoledaki
Copy link
Contributor

nikimanoledaki commented Jan 25, 2024

Requirements to consider:

  • Provide a script with steps to follow to reproduce this test
  • Set the duration of the idle test scenario to, for example, 15 minutes
  • Track and export the results of the metrics in a consistent manner

@nikimanoledaki
Copy link
Contributor

nikimanoledaki commented Jan 25, 2024

Proposal for benchmark steps & how to setup the benchmark environment: https://docs.google.com/document/d/19fzZW-IMv2kDNatKFHeHh7wqcEN0e2N60wzxvCGZd48/edit#heading=h.2uwb7llv9gl3

@AntonioDiTuri
Copy link
Contributor Author

Hey Niki! Thanks a lot for the proposals.

My take is that we could opt for the same strategy we choose for the deployment of the infra-component.
We could have a first step in which we have some simple bash script just to have a quick-and-dirty win and as soon as every component work we can design a well structured github workflow.

What do you think?

@nikimanoledaki nikimanoledaki added the priority/critical Top priority label Feb 7, 2024
@nikimanoledaki
Copy link
Contributor

nikimanoledaki commented Feb 7, 2024

@AntonioDiTuri sounds good! I created this issue to track the setup for the first benchmark test (idle): #50

+added it to the description of this issue!

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

No branches or pull requests

2 participants