Project

General

Profile

Actions

Feature #845

open

Memory consumption in stats.log

Added by Peter Manev about 8 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:

Description

It will be very helpful if some more stats can be added in the stats.log

May be at the bottom of each update/run - how much memory (in MB if possible) is Suricata using for flow, stream, reassembly and fragmentation.
Or in other words - mirror of the yaml settings for flow, stream, reassembly and fragmentation, but from actual physical memory consumption point of view.

Thank you

Actions #1

Updated by Victor Julien almost 8 years ago

  • Target version set to TBD
Actions #2

Updated by Andreas Herz over 5 years ago

  • Assignee set to OISF Dev
Actions #3

Updated by Andreas Herz over 2 years ago

This would be really helpful but would it also increase the load to calculate it each time?

Actions #4

Updated by Peter Manev over 2 years ago

Most of these mem stats are already in :

tcp.memuse                                    | Total                     | 2240000000
tcp.reassembly_memuse                         | Total                     | 384780288
http.memuse                                   | Total                     | 260882
ftp.memuse                                    | Total                     | 696
flow.memuse                                   | Total                     | 7612575672
Actions #5

Updated by Andreas Herz over 2 years ago

So we have still missing:

- dns
- defrag
- host table
- ippair

stream is covered by the tcp ones.
At least this is the list I could come up with based on possible memory settings in the suricata.yaml.

Do you see any others?

Actions #6

Updated by Peter Manev over 2 years ago

For some of those we have memcaps counters(dns for example) so it still helps a bit. Don't see any others for now.

Actions

Also available in: Atom PDF