Logging: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
=Messages from GNU GPL sniffer sensor service= | =Messages from GNU GPL sniffer sensor service= | ||
'''Voipmonitor''' by default uses 'daemon' facility of syslog to store status messages. | '''Voipmonitor''' by default uses 'daemon' facility of a syslog to store status messages. | ||
==Default location== | |||
it is stored to '''/var/log/syslog'''(on debian/ubuntu)or to '''/var/log/messages'''(on centos/rh) | |||
==Messages file Change== | |||
You can find useful to store status info from voipmonitor to different file: | You can find useful to store status info from voipmonitor to different file: | ||
For '''rsyslog''' use this in /etc/rsyslog.conf | For '''rsyslog''' use this in /etc/rsyslog.conf | ||
| Line 11: | Line 12: | ||
& ~ | & ~ | ||
=Status line details= | |||
==SQLq== | |||
C=CDR_queue | C=CDR_queue | ||
M=Message_queue | M=Message_queue | ||
| Line 21: | Line 21: | ||
Cl=Cleanspool queue | Cl=Cleanspool queue | ||
==tarQ=== | |||
number of files in a queue | number of files in a queue | ||
=tarB= | ==tarB=== | ||
MBs in tar buffer | MBs in tar buffer | ||
=tarCPU= | ==tarCPU== | ||
threads used for taring - its consumption | threads used for taring - its consumption | ||
=t2CPU= | ==t2CPU== | ||
pb:10.5/ - packetbuffer - out of the buffer | pb:10.5/ - packetbuffer - out of the buffer | ||
d:39.2/ - structs create for processing in t2 | d:39.2/ - structs create for processing in t2 | ||
| Line 43: | Line 43: | ||
rd:19.3/ - RTP - move to read queue | rd:19.3/ - RTP - move to read queue | ||
==Adding new thread is automatic== | ===Adding new thread is automatic=== | ||
'd' is running after pb, | 'd' is running after pb, | ||
if 'd' > 50%, new thread 's' (reasembles, sip parse) | if 'd' > 50%, new thread 's' (reasembles, sip parse) | ||
if 's' > 50%, new thread 'e' (callid | if 's' > 50%, new thread 'e' (callid search + structs create for calls), | ||
if 'e' > 50%, new thread 'c' (calls) | if 'e' > 50%, new thread 'c' (calls) | ||
if 'c' > 50%, new thread 'g' (registers) | if 'c' > 50%, new thread 'g' (registers) | ||
if 'g' > 50%, new thread 'r' (rtp) | if 'g' > 50%, new thread 'r' (rtp) | ||
==Threads removing== | ===Threads removing=== | ||
if 'r' < N remove 'r' | if 'r' < N remove 'r' | ||
if 'g' < N remove 'g' | if 'g' < N remove 'g' | ||
Revision as of 03:01, 15 February 2018
Messages from GNU GPL sniffer sensor service
Voipmonitor by default uses 'daemon' facility of a syslog to store status messages.
Default location
it is stored to /var/log/syslog(on debian/ubuntu)or to /var/log/messages(on centos/rh)
Messages file Change
You can find useful to store status info from voipmonitor to different file: For rsyslog use this in /etc/rsyslog.conf
if $programname == 'voipmonitor' and $syslogseverity <= '7' then /var/log/voipmon.log & ~
Status line details
SQLq
C=CDR_queue M=Message_queue R=Register_queue L=LiveSniffer_queue Cl=Cleanspool queue
tarQ=
number of files in a queue
tarB=
MBs in tar buffer
tarCPU
threads used for taring - its consumption
t2CPU
pb:10.5/ - packetbuffer - out of the buffer d:39.2/ - structs create for processing in t2 s:24.6/ - SIP - parse e:17.3/ - SIP - calls/messages search, struct creation c:6.8/ - process_packets - calls/messages g:6.4/ - process_packets - registers r:7.3/ - process_packets - RTP
rm:24.6/ - packets shift, prepare for processing rh:16.7/ - RTP - search hash rd:19.3/ - RTP - move to read queue
Adding new thread is automatic
'd' is running after pb, if 'd' > 50%, new thread 's' (reasembles, sip parse) if 's' > 50%, new thread 'e' (callid search + structs create for calls), if 'e' > 50%, new thread 'c' (calls) if 'c' > 50%, new thread 'g' (registers) if 'g' > 50%, new thread 'r' (rtp)
Threads removing
if 'r' < N remove 'r' if 'g' < N remove 'g' if 'c' < N remove 'c' if 'e' < N remove 'e' if 's' < N remove 's'