@Felix_Roessel and @warkolm
I tried to query with different sizes of the index (15GB, 30GB, 50GB etc). As mentioned above, I tried with two replicas (same problem) but not with more shards.
When I am waiting for the result of my query, I cannot do anything else with Kibana. Monitoring just freeze. So, looking at the stack monitoring I have noticed higher CPU utilization in node 1 where is the primary is stored. However, even giving more and more CPU the high utilization is the same - 100% CPU.
I cannot understand why this dashboard is consuming too much CPU. I think I gave for each server is enough to start. Now I have only this index with less than 24 hours of logs/data/netflow traffic ----- 3 data nodes (12 vCPU, 10 RAM -Xms5g m / -Xmx5g, no swap, ulimit open files) - each server is in a different disk (SAS 1TB). I also increase the number of threads
I think the question is, is there someone that uses Filebeat Netflow Module and it really works?
GET _cat/shards/filebeat-000001
filebeat-000001 0 p STARTED 38309542 23.2gb 172.20.11.43 elk-node-1
filebeat-000001 0 r STARTED 38308346 23.1gb 172.20.11.44 elk-node-2
GET _cat/indices/filebeat-000001
green open filebeat-000001 g0SBMcRgSoSBFgvOSr8wIg 1 1 38326478 0 46.4gb 23.2gb
GET filebeat-000001/_ilm/explain
{
"indices" : {
"filebeat-000001" : {
"index" : "filebeat-000001",
"managed" : true,
"policy" : "filebeat_policy",
"lifecycle_date_millis" : 1618274869201,
"age" : "16.93h",
"phase" : "hot",
"phase_time_millis" : 1618274869502,
"action" : "rollover",
"action_time_millis" : 1618274869884,
"step" : "check-rollover-ready",
"step_time_millis" : 1618274869884,
"phase_execution" : {
"policy" : "filebeat_policy",
"phase_definition" : {
"min_age" : "0ms",
"actions" : {
"rollover" : {
"max_size" : "30gb",
"max_age" : "1d"
},
"set_priority" : {
"priority" : 100
}
}
},
"version" : 1,
"modified_date_in_millis" : 1618267042453
}
}
}
}
--
--
--
--
--