Bad logstash performance

Why it happens?

count: 7964 - rate 1m: 1172.7211336354694 - _5m: 1426.257376894607 - 15m: 1473.5596592555096
2018-04-13T14:59:38.408Z
count: 14959 - rate 1m: 1190.877357320955 - _5m: 1425.8200749188456 - 15m: 1473.151019532127
2018-04-13T14:59:45.194Z
count: 14959 - rate 1m: 1008.0559195582182 - _5m: 1379.0761328519673 - 15m: 1456.8732742550358
2018-04-13T14:59:57.849Z
count: 14959 - rate 1m: 927.456218423565 - _5m: 1356.2820093066184 - 15m: 1448.8019748780591
2018-04-13T15:00:04.466Z
count: 21957 - rate 1m: 817.0298753428816 - _5m: 1312.5103068768226 - 15m: 1432.5237026199932
2018-04-13T15:00:21.028Z
count: 21957 - rate 1m: 636.3035067097685 - _5m: 1248.4984238616955 - 15m: 1408.846168449611
2018-04-13T15:00:38.915Z
count: 29652 - rate 1m: 610.0218254173948 - _5m: 1232.9467408137302 - 15m: 1402.745097292375
2018-04-13T15:00:46.248Z
count: 29848 - rate 1m: 561.0808800012021 - _5m: 1193.127889206105 - 15m: 1386.5212955863888
2018-04-13T15:00:59.426Z
count: 32847 - rate 1m: 519.067612411839 - _5m: 1163.7624653073547 - 15m: 1374.5053483693152

I think you will need to provide a lot more context, and probably some details about you configuration and setup if anyone is going to be able to give any kind of answer....

I have created a bad logstash filter with grok pattern. Now I removed it and I solved the issue.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.