Elastisearch client in Relay server #31
Conversation
Signed-off-by: Sibasish Behera <fangedhamster3114@gmail.com>
Signed-off-by: Sibasish Behera <fangedhamster3114@gmail.com>
| # storageClassName: "" | ||
| resources: | ||
| requests: | ||
| storage: 10Gi |
There was a problem hiding this comment.
Do we need 10Gi? I am not sure what kind of memory do we require here.
There was a problem hiding this comment.
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .kibana_1 UhiacNwdSyCdwrZ_WZOdRg 1 1 26 0 70.3kb 35.1kb
green open alert nai7xLdcRaKe-xStBA44qQ 1 1 4 0 77.4kb 38.7kb
I have done rough calulations for 5Gi in each instance , with some real data here , taking a count of 1000 alerts per hour and assuming a storage capacity of total 12 GB(from 3 instances - 1Gb each for elasticsearch itself) , it can sustain approximately 27 days of storage , for above scenario.
Here each alert is taking ~20kb .
I am not sure how many alerts per hour is practical ?
There was a problem hiding this comment.
Ideally we expect the alerts to be less (otherwise something is really bad), I would say 1000 alerts/hr should be fine.
@nyrahul wdyt?
|
I couldn't see the resolved comments to be addressed, can you please take a look? Also, please resolve the merge conflicts. |
i have resolved the suggestions comments and merge conflicts |
TheRealSibasishBehera
force-pushed
the
main
branch
from
d3bca66
to
3064eff
Compare
Signed-off-by: Sibasish Behera <fangedhamster3114@gmail.com>
Signed-off-by: Sibasish Behera <fangedhamster3114@gmail.com>
TheRealSibasishBehera
force-pushed
the
main
branch
from
3064eff
to
6bd058c
Compare
Changes Made
Fixes for kubearmor/KubeArmor#836