Ad Widget

Collapse

mysql windows agent configuration

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • humayunshafiq
    Junior Member
    • Dec 2012
    • 6

    #1

    mysql windows agent configuration

    Hi, i am new to Zabbix and for a last two day i am facing problem configuring the screen map of mysql server.

    i have already find the mysql linux agent configuration but could'nt find the windows agent configuration for mysql

    please help as i need this urgently to deploy on server
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    Your post is a little confusing. Are you looking for zabbix_agentd.conf file for Windows servers?
    (This has nothing to do with mysql)
    Last edited by tchjts1; 04-12-2012, 21:18.

    Comment

    • tchjts1
      Senior Member
      • May 2008
      • 1605

      #3
      I think that is what you are asking for. You can copy the below and place into a file called zabbix_agentd.conf

      Note that you will need to edit the parameters for Server=, ServerActive= and Hostname=

      (You can leave Hostname= blank if you are using Autoconfiguration)

      Code:
      # This is a config file for Zabbix Agent (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=c:\zabbix\zabbix_agentd.log
      
      ### Option: LogFileSize
      #	Maximum size of log file in MB.
      #	0 - disable automatic log rotation.
      #
      # Mandatory: no
      # Range: 0-1024
      # Default:
      # LogFileSize=1
      
      ### 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
      
      ### 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=0
      
      ### Option: LogRemoteCommands
      #	Enable logging of executed shell commands as warnings.
      #	0 - disabled
      #	1 - enabled
      #
      # Mandatory: no
      # Default:
      # LogRemoteCommands=0
      
      ##### 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.
      #	No spaces allowed.
      #	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=
      
      ### 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
      
      ##### 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=
      
      ### 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=
      
      ### Option: HostnameItem
      #	Item used for generating Hostname if it is undefined.
      #	Ignored if Hostname is defined.
      #
      # Mandatory: no
      # Default:
      # HostnameItem=system.hostname
      
      ### Option: RefreshActiveChecks
      #	How often list of active checks is refreshed, in seconds.
      #
      # Mandatory: no
      # Range: 60-3600
      # Default:
      # RefreshActiveChecks=120
      
      ### 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=100
      
      ### 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=100
      
      ############ ADVANCED PARAMETERS #################
      
      ### Option: Alias
      #	Sets an alias for parameter. It can be useful to substitute long and complex parameter name with a smaller and simpler one.
      #	For example, if you wish to retrieve paging file usage in percents from the server,
      #	you may use parameter "perf_counter[\Paging File(_Total)\% Usage]", or you may define an alias by adding the following line to configuration file
      #	Alias = pg_usage:perf_counter[\Paging File(_Total)\% Usage]
      #	After that you can use parameter name "pg_usage" to retrieve the same information.
      #	You can specify as many "Alias" records as you wish.
      #	Aliases cannot be used for parameters defined in "PerfCounter" configuration file records.
      #
      # Mandatory: no
      # Range:
      # Default:
      
      ### Option: Timeout
      #	Spend no more than Timeout seconds on processing
      #
      # Mandatory: no
      # Range: 1-30
      # Default:
      # Timeout=3
      
      ### 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=c:\zabbix\zabbix_agentd.userparams.conf
      # Include=c:\zabbix\zabbix_agentd\
      
      ####### 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>
      #	Note that shell command must not return empty string or EOL only.
      #	Example: UserParameter=system.test,echo 1
      #UserParameter=system.test,echo 1

      Comment

      • humayunshafiq
        Junior Member
        • Dec 2012
        • 6

        #4
        I already configure the zabbix_agentd.conf and it is working great for monitoring the server

        what i need is i have mysql install into that server and i need to monitor mysql too, i google it and find out that some kind of configuration are needed in zabbix_agentd.conf file.. now i am looking for that configuration.. or someone can guide me through configuring mysql in zabbix

        Comment

        • tchjts1
          Senior Member
          • May 2008
          • 1605

          #5
          Now I understand. One thing you might try doing is using PerfMon counters from that Windows server.

          With MySql up and running, bring up a DOS prompt and type this command: typeperf -qx > perfcounters.txt

          This will produce a text file of performance counters that you can enter into Zabbix and monitor. I would use an editor like Notepad++ and do a search for all instances of "MySql" and see what is available.

          You can further follow this thread for using those perfcounters:

          Comment

          • hammadbinmahmood
            Junior Member
            • Mar 2013
            • 1

            #6
            MySQL Monitoring using Windows based Zabbix Agent

            I tried to search for a solution to the same problem and also saw your post. My search lead me to the development of VBScript files to solve the problem of MySQL monitoring using Windows Zabbix Agent.

            First Step:
            ========
            You will need to create a VBScript file for mysql_status[*] user parameter with *.vbs extension with the following code:

            Set objFS = CreateObject("Scripting.FileSystemObject")
            Set objArgs = WScript.Arguments
            str1 = getCommandOutput("C:\MySQL\bin\mysqladmin -u root -P5000 extended-status")
            Arg = objArgs(0)
            str2 = Split(str1,"|")

            For i = LBound(str2) to UBound(str2)

            If Trim(str2(i)) = Arg Then
            WScript.Echo TRIM(str2(i+1))
            Exit For
            End If
            next


            Function getCommandOutput(theCommand)

            Dim objShell, objCmdExec
            Set objShell = CreateObject("WScript.Shell")
            Set objCmdExec = objshell.exec(thecommand)
            getCommandOutput = objCmdExec.StdOut.ReadAll

            end Function

            I saved this file at the location C:\Zabbix\Scripts with the name "MySQL_Ext-Status_Script.vbs"

            Second Step:
            ==========
            You will need to create a VBScript file for mysql.ping user parameter with *.vbs extension with the following code:

            Set objFS = CreateObject("Scripting.FileSystemObject")
            Set objArgs = WScript.Arguments
            str1 = getCommandOutput("C:\MySQL\bin\mysqladmin -u root -P5000 ping")

            If Instr(str1,"alive") > 0 Then
            WScript.Echo 1
            Else
            WScript.Echo 0
            End If

            Function getCommandOutput(theCommand)

            Dim objShell, objCmdExec
            Set objShell = CreateObject("WScript.Shell")
            Set objCmdExec = objshell.exec(thecommand)
            getCommandOutput = objCmdExec.StdOut.ReadAll

            end Function

            I saved this file at the location C:\Zabbix\Scripts with the name "MySQL_Ping.vbs"

            Third Step:
            ========
            Modify your zabbix_agentd.conf file and add the following lines to the conf file under the User Parameters Config Section:

            UserParameter=mysql.status[*], cscript /nologo C:\Zabbix\Scripts\MySQL_Ext-Status_Script.vbs $1

            UserParameter=mysql.ping, cscript /nologo C:\Zabbix\Scripts\MySql_Ping.vbs

            Fourth Step:
            =========
            Restart your Windows Zabbix Agent. Add host information in Zabbix Server front-end with Template "Template App MySQL".

            The good thing about this configuration is that the command
            "mysqladmin -u root -P5000 extended-status"
            if run on a command prompt offers so many parameters for MySQL Monitoring.
            You can monitor each individual parameter through Zabbix just by adding an item in the Host Configuration with Key: mysql_status[parameterName].

            Regards

            Comment

            Working...