Ad Widget

Collapse

Zabbix is slooow (log-file monitoring)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • arcenciel4
    Member
    • Jun 2014
    • 36

    #1

    Zabbix is slooow (log-file monitoring)

    Hi! Zabbix monitors 2 log-file on presence some regular expression on windows. Average log size is 100 MB (+ -20 MB). Sometimes an entry 1500 lines per minute. Zabbix find reg exp with big delay.
    How to set Zabbix on fast work?
    Agent config file:
    Code:
    # This is a config file for the Zabbix agent daemon (Windows)
    # To get more information about Zabbix, go to http://www.zabbix.com
    
    ############ GENERAL PARAMETERS #################
    
    ### Option: LogFile
    #	Name of log file.
    #	If not set, Windows Event Log is used.
    #
    # Mandatory: no
    # Default:
    # LogFile=
    
    LogFile=J:\Zabbix-Agent\log\zabbix_agentd.log
    
    ### Option: LogFileSize
    #	Maximum size of log file in MB.
    #	0 - disable automatic log rotation.
    #
    # Mandatory: no
    # Range: 0-1024
    # Default:
     LogFileSize=50
    
    ### Option: DebugLevel
    #	Specifies debug level 
    #	0 - no debug
    #	1 - critical information
    #	2 - error information
    #	3 - warnings
    #	4 - for debugging (produces lots of information)
    #
    # Mandatory: no
    # Range: 0-4
    # Default:
    # DebugLevel=3
    DebugLevel=4
    
    ### Option: SourceIP
    #	Source IP address for outgoing connections.
    #
    # Mandatory: no
    # Default:
    # SourceIP=
    
    ### Option: EnableRemoteCommands
    #	Whether remote commands from Zabbix server are allowed.
    #	0 - not allowed
    #	1 - allowed
    #
    # Mandatory: no
    # Default:
     EnableRemoteCommands=1
    
    ### Option: LogRemoteCommandsc 
    #	Enable logging of executed shell commands as warnings.
    #	0 - disabled
    #	1 - enabled
    #
    # Mandatory: no
    # Default:
    LogRemoteCommands=1
    
    ##### Passive checks related
    
    ### Option: Server
    #	List of comma delimited IP addresses (or hostnames) of Zabbix servers.
    #	Incoming connections will be accepted only from the hosts listed here.
    #	If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally.
    #
    # Mandatory: no
    # Default:
    # Server=
    
    Server=195.189.***.7
    
    ### Option: ListenPort
    #	Agent will listen on this port for connections from the server.
    #
    # Mandatory: no
    # Range: 1024-32767
    # Default:
    ListenPort=10050
    
    ### Option: ListenIP
    #       List of comma delimited IP addresses that the agent should listen on.
    #       First IP address is sent to Zabbix server if connecting to it to retrieve list of active checks.
    #
    # Mandatory: no
    # Default:
    # ListenIP=0.0.0.0
    
    
    ### Option: StartAgents
    #	Number of pre-forked instances of zabbix_agentd that process passive checks.
    #	If set to 0, disables passive checks and the agent will not listen on any TCP port.
    #
    # Mandatory: no
    # Range: 0-100
    # Default:
    # StartAgents=3
    StartAgents=40
    
    ##### Active checks related
    
    ### Option: ServerActive
    #	List of comma delimited IP:port (or hostname:port) pairs of Zabbix servers for active checks.
    #	If port is not specified, default port is used.
    #	IPv6 addresses must be enclosed in square brackets if port for that host is specified.
    #	If port is not specified, square brackets for IPv6 addresses are optional.
    #	If this parameter is not specified, active checks are disabled.
    #	Example: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1]
    #
    # Mandatory: no
    # Default:
    # ServerActive=
    ServerActive=195.189.***.7:10051
    
    
    ### Option: Hostname
    #	Unique, case sensitive hostname.
    #	Required for active checks and must match hostname as configured on the server.
    #	Value is acquired from HostnameItem if undefined.
    #
    # Mandatory: no
    # Default:
    # Hostname=
    
    Hostname=MT4_MTXAPCL1
    
    ### Option: HostnameItem
    #	Item used for generating Hostname if it is undefined.
    #	Ignored if Hostname is defined.
    #
    # Mandatory: no
    # Default:
    # HostnameItem=system.hostname
    
    ### Option: HostMetadata
    #	Optional parameter that defines host metadata.
    #	Host metadata is used at host auto-registration process.
    #	An agent will issue an error and not start if the value is over limit of 255 characters.
    #	If not defined, value will be acquired from HostMetadataItem.
    #
    # Mandatory: no
    # Range: 0-255 characters
    # Default:
    # HostMetadata=
    
    ### Option: HostMetadataItem
    #	Optional parameter that defines an item used for getting host metadata.
    #	Host metadata is used at host auto-registration process.
    #	During an auto-registration request an agent will log a warning message if
    #	the value returned by specified item is over limit of 255 characters.
    #	This option is only used when HostMetadata is not defined.
    #
    # Mandatory: no
    # Default:
    # HostMetadataItem=
    
    ### Option: RefreshActiveChecks
    #	How often list of active checks is refreshed, in seconds.
    #
    # Mandatory: no
    # Range: 60-3600
    # Default:
     RefreshActiveChecks=60
    
    ### Option: BufferSend
    #	Do not keep data longer than N seconds in buffer.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
     BufferSend=5
    
    ### Option: BufferSize
    #	Maximum number of values in a memory buffer. The agent will send
    #	all collected data to Zabbix server or Proxy if the buffer is full.
    #
    # Mandatory: no
    # Range: 2-65535
    # Default:
     BufferSize=30
    
    ### Option: MaxLinesPerSecond
    #	Maximum number of new lines the agent will send per second to Zabbix Server
    #	or Proxy processing 'log', 'logrt' and 'eventlog' active checks.
    #	The provided value will be overridden by the parameter 'maxlines',
    #	provided in 'log', 'logrt' or 'eventlog' item keys.
    #
    # Mandatory: no
    # Range: 1-1000
    # Default:
     MaxLinesPerSecond=1000
    
    ############ ADVANCED PARAMETERS #################
    
    ### Option: Alias
    #	Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.
    #	Multiple Alias parameters may be present. Multiple parameters with the same Alias key are not allowed.
    #	Different Alias keys may reference the same item key.
    #	For example, to retrieve paging file usage in percents from the server:
    #	Alias=pg_usage:perf_counter[\Paging File(_Total)\% Usage]
    #	Now shorthand key pg_usage may be used to retrieve data.
    #	Aliases can be used in HostMetadataItem but not in HostnameItem or PerfCounter parameters.
    #
    # Mandatory: no
    # Range:
    # Default:
    
    ### Option: Timeout
    #	Spend no more than Timeout seconds on processing
    #
    # Mandatory: no
    # Range: 1-30
    # Default:
     Timeout=30
    
    ### Option: PerfCounter
    #	Syntax: <parameter_name>,"<perf_counter_path>",<period>
    #	Defines new parameter <parameter_name> which is an average value for system performance counter <perf_counter_path> for the specified time period <period> (in seconds).
    #	For example, if you wish to receive average number of processor interrupts per second for last minute, you can define new parameter "interrupts" as following:
    #	PerfCounter = interrupts,"\Processor(0)\Interrupts/sec",60
    #	Please note double quotes around performance counter path.
    #	Samples for calculating average value will be taken every second.
    #	You may run "typeperf -qx" to get list of all performance counters available in Windows.
    #
    # Mandatory: no
    # Range:
    # Default:
    
    ### Option: Include
    #	You may include individual files in the configuration file.
    #
    # Mandatory: no
    # Default:
    # Include=
    
     #Include=d:\Alfa monitoring\zabbix\zabbix_agentd.userparams.conf
    
    ####### USER-DEFINED MONITORED PARAMETERS #######
    
    ### Option: UnsafeUserParameters
    #	Allow all characters to be passed in arguments to user-defined parameters.
    #	0 - do not allow
    #	1 - allow
    #
    # Mandatory: no
    # Range: 0-1
    # Default:
    # UnsafeUserParameters=0
    
    ### Option: UserParameter
    #	User-defined parameter to monitor. There can be several user-defined parameters.
    #	Format: UserParameter=<key>,<shell command>
    #
    # Mandatory: no
    # Default:
    # UserParameter=
    UserParameter=notation.res,cluster res
    You are my last hope!
  • ingus.vilnis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Mar 2014
    • 908

    #2
    Hi,

    Mind to share your log item settings as well for us to check?

    What do you mean by big delay in finding regexps? It might not be that Zabbix is slow, it looks more than a performance tuning issue.

    By looking at the agent log, I have the following notes:
    • DebugLevel=4 - why do you need that on a daily basis? When reading many values, it takes resources to write in the file. It is advised to use level 4 only temporary for debug purposes.
    • StartAgents=40 - again, why that many? Very huge machine with lots of checks?
    • BufferSize=30 - decreased from default 100. Strange. Not sure, but could affect performance
    • Timeout=30 - why that many? Are you having timeout issues?
    • Unnecessary spaces before the parameter names.


    Taking into account all this, I can't even imagine what's going on in your zabbix_server.conf It is very possible that some parameters affect the performance there as well.

    Best Regards,
    Ingus

    Comment

    • arcenciel4
      Member
      • Jun 2014
      • 36

      #3
      Originally posted by ingus.vilnis
      Hi,

      Mind to share your log item settings as well for us to check?

      What do you mean by big delay in finding regexps? It might not be that Zabbix is slow, it looks more than a performance tuning issue.

      By looking at the agent log, I have the following notes:
      • DebugLevel=4 - why do you need that on a daily basis? When reading many values, it takes resources to write in the file. It is advised to use level 4 only temporary for debug purposes.
      • StartAgents=40 - again, why that many? Very huge machine with lots of checks?
      • BufferSize=30 - decreased from default 100. Strange. Not sure, but could affect performance
      • Timeout=30 - why that many? Are you having timeout issues?
      • Unnecessary spaces before the parameter names.


      Taking into account all this, I can't even imagine what's going on in your zabbix_server.conf It is very possible that some parameters affect the performance there as well.

      Best Regards,
      Ingus
      In zabbix server config I just changed StartPollers on 20.
      My items on one of two hosts. On second bit more.

      Triggers use Nodata function.
      How set configs to get the maximum performance?
      Thancks for answer.
      Last edited by arcenciel4; 18-07-2014, 10:59.

      Comment

      Working...