Please enter a valid email address. The download links will be emailed to you.
The download links for
MONyog have been sent to
Back to Topics

FAQ

Table of content:

1. Monyog is licensed per server. Does that mean Monyog servers or MySQL servers?

2. Do I need to install Monyog on the same host as MySQL?

3. What operations system does Monyog require?

4. How do I upgrade Monyog?

5. Why should I upgrade?

6. I have installed Monyog. What now? How do I get the reports?

7. How can Monyog 'know all what it does'?

8. Where does Monyog store data?

9. How does Monyog store its data?

10. Can I move a Monyog installation to another computer while keeping the data stored in Monyog database?

11. Can Monyog be configured as a virtual host in my 'ordinary' Apache webserver?

12. How can I access Monyog pages proxying through other webservers?

13. How can I access Monyog pages proxying through nginx?

14. Can I access Monyog pages using encrypted connection such as "https"?

15. What are the major differences between other major MySQL Monitoring Tool and Monyog?

16. Can I trust the expertise of Monyog developers?

17. How does Monyog connect to MySQL?

18. Windows warns after installation that Monyog may not have installed properly.

19. I would like to use SSH-tunnel, but my Windows server does not support it. Can that be fixed?

20. Monyog throws an error when trying to connect to MySQL.

21. Failed to connect to MySQL: Can't connect to local MySQL server through socket... What can i do about this?

22. Monyog is taking up too much of system resources with the PROCESSLIST-based sniffer.

23. Why is display of queries truncated in Query Analyzer?

24. The servers that I have registered do not display. What is wrong?

25. Now, anybody will be able to connect to my Monyog server and retrieve details about MySQL servers.

26. I have the same server registered twice. Metrics are reported different. Why?

27. Will it affect the performance of a server if Monyog connects to it?

28. Is it possible to avoid that Monyog itself influences certain counters reported?

29. Can I customize Monyog counters?

30. I cannot sit watching a browser all the time - Can I get alerts if something goes wrong?

31. Monyog cannot identify if destination of the log file is on a "Mapped Network Drive". Why?

32. Failed to connect to MySQL: Unknown MySQL server host... What can i do about this?

33. How can I monitor the queries from the file based RDS/Aurora Query logs?

34. What are future plans for Monyog?

35. How do I get help and report problems?

36. Can I use the keys generated from PuTTY for SSH connection?

37. Steps to auto-start Monyog service with OS reboot in Ubuntu and Debian systems.

38. How to upgrade Monyog without losing your data or configuration?

1. Monyog is licensed per server. Does that mean Monyog servers or MySQL servers?

A: It means MySQL servers. You may install as many instances of Monyog as you like as long as the total number of MySQL servers monitored does not exceed your license.

2. Do I need to install Monyog on the same host as MySQL?

A: MySQL servers, Monyog server(s) and Clients (browser) can be installed independently everywhere where a TCP connection (like an Internet/Intranet connection) is available. Available TCP connections is all what is required. Put one on the Moon if you like (but don't ask us to pay for the connection!). Regarding installing Monyog on the same host as MySQL please refer to Connects to/Monitors MySQL on any platform. For further details see also Installation.

3. What operations system does Monyog require?

A: Currently we support Windows (do not support Windows 2000) and Linux operating systems. Those are the Operating Systems where Monyog itself will have to be installed. The Monyog client functionalities only require an Internet browser and any platform (including platforms for handheld devices like mobile phone, PDA, tablet PC etc.) will do. There are also no restriction as regards the platforms the MySQL servers that Monyog connect to - it can be any. Additionally, Monyog is able to retrieve OS data from Linux Operation Systems.

4. How do I upgrade Monyog?

A: This is actually a license-related question and a technical question as well.

  • License: Monyog ships with 1 year of free upgrades. After that you will be offered an upgrade with discount. Our website will always tell the terms and conditions. Also our website has a Portal for registered users from where you can download free upgrades and purchase upgrades after the expiry of the free upgrade period.

  • Technical: The automatic installers (the Windows version and the RPM build for Redhat type Linux) handles everything automatically. The gz-compressed build for other Linux's will required that you run execute a few installation scripts from a command shell. We constantly improve and simplify this. After extracting the tar.gz package, you will get a file called README. Please refer to that for details.

  • Need to monitor more servers: You can anytime upgrade your Monyog installation from monitoring a certain number of servers to a higher numbers by opening the License Manager and enter a new license key. If you need this please first contact us through our ticket system. We will consider the value of your existing license and compensate you (details will depend on what license you have and what you need and how old your existing license is).

Note

Don't forget to backup whatever JavaScript you have edited,as they will be overwritten when upgrading.

5. Why should I upgrade?

A: Every new release adds features, fixes bugs, improves performance, stability, the GUI interface etc. Why should you NOT upgrade? Refer to Version History for details.

6. I have installed Monyog. What now? How do I get the reports?

A: What you installed was the Monyog service. This service is basically a webserver program. You connect to the service with an Internet browser by specifying the host where it is installed and the port that was specified when installing.

7. How can Monyog 'know all what it does'?

A: Monyog queries the MySQL servers about almost anything the server 'knows' except for data stored on those servers. The MySQL servers themselves store and maintain records of server configuration, users, history and much more. Monyog retrieves this information, organizes it, calculates on it and reports.

8. Where does Monyog store data?

A: This depends on the Operating system.

- Windows XP/2003:

Data folder:

   Windows XP/2003: {System_drive}:\Documents and Settings\All Users\Application Data\Webyog\MONyog\Data

MONyog.ini + MONyog.log + preferences.config are in:

   Windows XP/2003: {System_drive}:\Documents and Settings\All Users\Application Data\Webyog\MONyog

- Windows Vista/2008:

Data folder:

   Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog\Data

MONyog.ini + MONyog.log + preferences.config are in:>

   Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog

- Linux RPM build:

Data folder: The connection configuration and collected data are kept here. There will be directories named like 0001, 0002, 0003, etc.

   /usr/local/MONyog/data/

Installation file:

   /usr/local/MONyog/MONyog.ini

Log file:

   /usr/local/MONyog/MONyog.log

Configuration file:

   /usr/local/MONyog/preferences.config

- Linux .gz archive:

If you have extracted Monyog package in a directory called MONyog the data stored will be in:

Data folder: The connection configuration and collected data are kept here. There will be directories named like 0001, 0002, 0003, etc.

   MONyog/data/

Installation file:

   MONyog/MONyog.ini

Log file:

   MONyog/MONyog.log

Configuration file:

   MONyog/preferences.config

The data folder specified above is the default settings only. You can store in any position on any mapped/mounted drive that is writeable.

9. How does Monyog store its data?

A: Except for two plain text files: the Monyog log file and a very small .ini file (that contains information about the port on which Monyog listens, The Monyog administrator password and the path to the data folder), everything is kept in high-performance database files (SQLite format).

10. Can I move a Monyog installation to another computer while keeping the data stored in Monyog database?

A: Yes, this is quite simple actually. Just install Monyog on the 2nd machine. After install stop the running Monyog service and copy the ..\MONyog\Data folder from the old installation. You may also copy the MONyog.log if you want. All the connection configuration and the data will be in 'data' directory. The error log is MONyog.log and setting are stored in 'MONyog.ini' and 'preferences.config'. If you have made any changes to monitors they will be stored in 'Counters.def' and for CSO's in 'udo.def'. Copy all of them from your old installation onto new PC. After that start the service again.

11. Can Monyog be configured as a virtual host in my 'ordinary' Apache webserver?

A: Yes... at least with Apache this is possible. In your Apache configuration file (httpd.conf) add something like this (where 'ip1.ip2.ip3.ip4' is the IP address you reserve for Monyog).

   <VirtualHost *:80> 
       ServerName  monyog.mydomain.com
       ServerAlias http://monyog.mydomain.com
       Redirect permanent /  https://monyog.mydomain.com
   </VirtualHost>

   NameVirtualHost *:443 
   <VirtualHost *:443> 
       ServerName  monyog.mydomain.com
       ProxyPreserveHost On 
       ProxyPass /  http://127.0.0.1:<MONyog-Port>/ 
       ProxyPassReverse /  http://127.0.0.1:<MONyog-Port>/ 
       SSLEngine On 
       SSLCertificateFile <path-to-ssl-certificate.crt> 
       SSLCertificateKeyFile <path-to-ssl-key.key> 
   </VirtualHost>

And run the following command on the machine running apache server:

   /usr/sbin/setsebool httpd_can_network_connect=1

After changing the configuration, restart the apache server.

12. How can I access Monyog pages proxying through other webservers?

A: We can also access Monyog using Apache proxy. You need to follow these simple steps to configure your Apache server to support proxy.

Here, we will setup Proxy in system A and we assume that Monyog is installed in system B, now you can access Monyog using, "http:///monyog/".

Configurations on system-A:

  1. Please check whether you have libxml2 installed in your system.
  2. Download mod_proxy_html.c from http://apache.webthing.com/
  3. Now build mod_proxy_html with apxs, apxs -c -I/usr/include/libxml2 -i mod_proxy_html.c
  4. You need to load the following modules, so add the following entries in [/etc/httpd/conf/httpd.conf].

      LoadModule proxy_module modules/mod_proxy.so 
      LoadModule proxy_http_module modules/mod_proxy_http.so 
      LoadModule headers_module modules/mod_headers.so 
      LoadModule deflate_module modules/mod_deflate.so 
      LoadFile /usr/lib/libxml2.so 
      LoadModule proxy_html_module modules/mod_proxy_html.so
    
  5. Add the following configuration in your Apache configuration file [/etc/httpd/conf/httpd.conf]

ProxyRequests Off

         <Proxy *>
             Order deny, allow
             Allow from all
             </Proxy>
             ProxyHTMLExtended On
             ProxyPass      /monyog/  http://<ip-system-B>:5555/
             ProxyHTMLURLMap http://<ip-system-B>:5555/ /monyog/
             <Location /monyog/>       
                   ProxyPassReverse /
                   SetOutputFilter  proxy-html
                   ProxyHTMLURLMap  /      /monyog/
                   RequestHeader    unset  Accept-Encoding
             </Location>

13. How can I access Monyog pages proxying through nginx?

A: You can also access Monyog using nginx proxy. You need to follow these simple steps to configure your nginx server to support proxy. Here, we will setup Proxy in system A and we assume that Monyog is installed in system B, now you can access Monyog both over HTTP("http://") and HTTPS("https://").

Configuration of System A:

  1. Install nginx on your system.

  2. Create directories

    a. /var/log/nginx

    b. /var/www/cache

  3. Configure nginx: Open nginx.conf found in /etc/nginx and add the following in the http section:

     proxy_cache_path  /var/www/cache levels=1:2 keys_zone=my-cache:8m max_size=1000m inactive=600m;
     proxy_temp_path /var/www/cache/tmp;
    

    A sample nginx.conf would like the following:

     user  nginx;
     worker_processes  1;
     error_log  /var/log/nginx/error.log debug;
     pid        /var/run/nginx.pid;
     events {
        worker_connections  1024;
     }
     http {
       include       /etc/nginx/mime.types;
       default_type  application/octet-stream;
       log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                                      '$status $body_bytes_sent "$http_referer" '
                                      '"$http_user_agent" "$http_x_forwarded_for"';
       access_log  /var/log/nginx/access.log  main;
       sendfile        on;
       #tcp_nopush     on;
       keepalive_timeout  0;
       proxy_cache_path  /var/www/cache levels=1:2 keys_zone=my-cache:8m max_size=1000m inactive=600m;
       proxy_temp_path /var/www/cache/tmp;
       include /etc/nginx/conf.d/*.conf;
     }
    
  4. Put your SSL certificates in /etc/nginx/conf/

  5. Create a monyog.conf file inside /etc/nginx/conf.d/ and add the following:

     server {
          server_name _;
          listen 80;
          location / {
                 proxy_pass http://<ip-system-b>:5555;
                 proxy_redirect     off;
                 proxy_cache my-cache;
                 proxy_cache_valid  200 302  0m;
                 proxy_cache_valid  404      0m;
                 proxy_set_header   Host             $host;
                 proxy_set_header   X-Real-IP        $remote_addr;
                 proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;
                 proxy_max_temp_file_size 0;
                 client_max_body_size       10m;
                 client_body_buffer_size    128k;
                 proxy_connect_timeout      9000;
                 proxy_send_timeout         9000;
                 proxy_read_timeout         9000;
                 proxy_buffer_size          4k;
                 proxy_buffers              4 32k;
                 proxy_busy_buffers_size    64k;
                 proxy_temp_file_write_size 64k;
           }
     }
     server {
          server_name _;
          listen 443;
          ssl on;
          ssl_certificate /etc/nginx/conf/<certificate_name>.crt; 
          ssl_certificate_key /etc/nginx/conf/<certificate_key>.key; 
          location / { 
                 proxy_pass http://<ip-system-b>:5555; 
                 proxy_redirect off; 
                 proxy_cache my-cache;
                 proxy_cache_valid 200 302 0m; 
                 proxy_cache_valid 404 0m; 
                 proxy_set_header Host $host;
                 proxy_set_header X-Real-IP $remote_addr;
                 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                 proxy_max_temp_file_size 0; 
                 client_max_body_size 10m; 
                 client_body_buffer_size 128k;
                 proxy_connect_timeout 9000; 
                 proxy_send_timeout 9000; 
                 proxy_read_timeout 9000;
                 proxy_buffer_size 4k; 
                 proxy_buffers 4 32k;
                 proxy_busy_buffers_size 64k; 
                 proxy_temp_file_write_size 64k; 
           } 
     }
    

14. Can I access Monyog pages using encrypted connection such as "https"?

A: Yes... you can access Monyog using "https", you may acquire a certificate from a certificate authority, such as Verisign or you may use the OpenSSL package to create your own certificate and configure your Apache webserver for "https".

Here are the steps you may follow to setup "https" in your Apache webserver.

  1. Create a directory

    mkdir sslcert
    

    Now protect the directory,

    chmod 0700 sslcert
    
  2. Create two subdirectories

    mkdir certs private
    
  3. Create a database to keep track of each certificate

    echo '100001' >serial
    touch certindex.txt
    
  4. Create a custom config file for OpenSSL to use similar to openssl.cnf in your /etc/pki/tls folder.

            dir = .
            [ ca ]
            default_ca = CA_default
            [ CA_default ]
            serial = $dir/serial
            database = $dir/certindex.txt
            new_certs_dir = $dir/certs
            certificate = $dir/cacert.pem
            private_key = $dir/private/cakey.pem
            default_days = 365
            default_md = md5
            preserve = no
            email_in_dn = no
            nameopt = default_ca
            certopt = default_ca
            policy = policy_match
            [ policy_match ]
            countryName = match
            stateOrProvinceName = match
            organizationName = match
            organizationalUnitName = optional
            commonName = supplied
            emailAddress = optional
            [ req ]
            default_bits = 1024 # Size of keys
            default_keyfile = key.pem # name of generated keys
            default_md = md5 # message digest algorithm
            string_mask = nombstr # permitted characters
            distinguished_name = req_distinguished_name
            req_extensions = v3_req
            [ req_distinguished_name ]
            0.organizationName = Organization Name (company)
            organizationalUnitName = Organizational Unit Name (department, division)
            emailAddress = Email Address
            emailAddress_max = 40
            localityName = Locality Name (city, district)
            stateOrProvinceName = State or Province Name (full name)
            countryName = Country Name (2 letter code)
            countryName_min = 2
            countryName_max = 2
            commonName = Common Name (hostname, IP, or your name)
            commonName_max = 64
            0.organizationName_default = My Company
            localityName_default = My Town
            stateOrProvinceName_default = State or Providence
            countryName_default = US
            [ v3_ca ]
            basicConstraints = CA:TRUE
            subjectKeyIdentifier = hash
            authorityKeyIdentifier = keyid:always,issuer:always
            [ v3_req ]
            basicConstraints = CA:FALSE
            subjectKeyIdentifier = hash
    
  5. Create a root certificate All other certificates you create will be based of this. Since this is not a commercial certificate software may complain when they use your certificates. You may give people the "public" certifcate and your certifcate will work like commercial ones when they import it. To create, while in the 'sslcert' directory type:

    openssl req -new -x509 -extensions v3_ca -keyout private/cakey.pem -out cacert.pem -days 365 -config ./openssl.cnf
    

    You will be prompted for information and a password. Do not lose this password, make sure it is a secure one and back up the two files that are created.

    The two files that are created are cacert.pem, which is the one you can give to others for import in their browsers and cakey.pem, which will be in the private directory.

  6. Create a key and signing request

    openssl req -new -nodes -out name-req.pem -keyout private/name-key.pem -config ./openssl.cnf
    

    You will be prompted for information. The critical part is the "Common Name". This must be the server's hostname, such as mail.your.domain or the IP address. If you want to cover all subdomains you can enter *.your.domain. Use the "Organizational Unit" to remind you what the certificate is for, such as "Web Server". This will generate two files,

    • name-req.pem - the request

    • name-key.pem - the private key in the private directory

  7. Sign the request This will generate the certificate,

    openssl ca -out name-cert.pem -config ./openssl.cnf -infiles name-req.pem
    

    You will be prompted for the password used when creating the root certificate. Two files are created,

    • name-cert.pem - which is the certificate

    • <number.pem> - a copy of it in the certs directory

  8. Copy to the correct location For apache 2.x on Red Hat using the default location, the directory is:

    • For the name-key.pem:

       cp name-key.pem /etc/httpd/conf/ssl.key/
      
    • For the certificate:

       cp name-cert.pem /etc/httpd/conf/ssl.crt/
      
  9. Create a Virtual Host

         <VirtualHost ip-system-A>:443> DocumentRoot /var/www/html 
         ServerName myserver 
         ErrorLog /etc/httpd/logs/ssl_error_log 
         TransferLog /etc/httpd/logs/ssl_access_log 
         SSLEngine On 
         SSLCertificateFile /etc/httpd/conf/ssl.crt/name-cert.pem 
         SSLCertificateKeyFile /etc/httpd/conf/ssl.key/name-key.pem 
          </VirtualHost>
    
  10. Configure proxy in Apache described in FAQ 13 and restart Apache.

    Edit the Hosts file [/etc/hosts]

      <ip-system-A> myserver
    

15. What are the major differences between other major MySQL Monitoring Tool and Monyog?

A: They have similarities (in which they both differ from server-side scripts used for monitoring): they both make use of a HTTP service, a database and both use a web-browser for reporting. Important differences are however,

  • Monyog is distributed with a perpetual license and is not bundled with anything else. But other MySQL Monitoring Tools are available only as part of a larger support package with periodical license terms.
  • Monyog needs no installation (of 'agents') on the server where the MySQL servers are running. Other does.
  • Monyog 'has everything in itself' - the webserver, the database, the MySQL client. It does not depend on the existence of other webservers, runtimes/Virtual Machines (like JAVA) and needs no separate database install. Other monitoring tools requires a full JDK (java), a TOMCAT server and a MySQL server instance for itself. Due to this simplified architecture install, configuration and first of all maintenance and upgrade is much simpler with Monyog. Download packages and disk storage required are much smaller with Monyog.

16. Can I trust the expertise of Monyog developers?

A: Monyog is developed by the Webyog Softworks that also created the most popular GUI for data management with the MySQL server - SQLyog Enterprise. We have more than 5 years of experience with designing MySQL related software. We have expanded our team with highly qualified developers ever since we started. We are devoted to constantly extending our knowledge and understanding of MySQL internals. What more would you expect?

17. How does Monyog connect to MySQL?

A: Monyog uses the most proved and most efficient way of connecting: the native MySQL client library (the C-API) that is compiled into Monyog. Nothing else required: no separate client instance, no database abstraction layer (like ODBC/JDBC/ADO/.NET) and no webserver extensions (like PHP). Additionally, the connection can be 'wrapped' in a SSH tunnel. Also the Monyog implementation for this does not involve any other program (like Putty) running.

18. Windows warns after installation that Monyog may not have installed properly.

A: This may happen on recent versions of Windows (Vista and higher) if you install a recent version of Monyog on top of an older version. The reason for this is that recent versions of Windows include a software called "Program Compatibility Assistant" (PCA) which tries to detect if an installer is running. It warns the user that the software might not have been correctly installed if the installer does not register a new uninstaller. The PCA is unable to detect changes made to an existing, registered uninstaller, which is what the new Monyog installers do. And thus, the warning is displayed. You can safely ignore this warning, but if it bothers you, you may just uninstall Monyog before upgrading to 3.5+. All collected data in the Monyog data folder will still be available after reinstall. However, you should -

  • Backup the connections.data file before uninstalling
  • Restore the old connections.data after the new install. After a restart, Monyog will recognize connection settings in the old connections.data.

19. I would like to use SSH-tunnel, but my Windows server does not support it. Can that be fixed?

A: Yes, SSH support can be installed on Windows. You may install a complete Cygwin (Unix command line implementation for Windows). Alternatively, there are small packages available that support only a small subset of Cygwin (like SSH packages). Installation details depends on the exact Windows version.

20. Monyog throws an error when trying to connect to MySQL.

A: Please go through Error when trying to connect to MySQL. The same as here applies to Monyog as the client code is exactly the same in both programs. Observe however that everything related to HTTP-tunneling with SQLyog is not relevant for Monyog.

21. Failed to connect to MySQL: Can't connect to local MySQL server through socket... What can i do about this?

A: Ensure that the host specified resolves to an IP-adress. This error occurs with some Linux distributions (most important Debian) when specifying 'lcoalhost'. The system will map this to a Unix SOCKET file. Monyog connects through TCP and not to SOCKET. Try the ip '127.0.0.1' instead!

22. Monyog is taking up too much of system resources with the PROCESSLIST-based sniffer.

A: You may have noticed that, while using the PROCESSLIST-based sniffer, Monyog increases the load on the CPU as well as the I/O subsystem of the system on which it is installed - even when the MySQL server is idle. Don't panic: it's normal. When using the PROCESSLIST-based sniffer, Monyog continually queries the MySQL server at the end of each time interval, which can be specified by you. It then retrieves the results and stores them in an internal sniffer database before displaying the results back to you. Now, if you set a very short time interval, one that almost approaches 0, then in actuality Monyog will almost be stuck in an infinite loop! Consequently, the load on the CPU and I/O subsystem will increase exponentially. We generally recommend an interval of not more than 0.1sec times the number of servers for which Processlist-based sniffers are enabled. However, if you're worried that you may miss out on some important queries running on the MySQL server, use the MySQL Proxy. The LUA script supplied with Monyog should handle the task for you very well! For more information on using MySQL Proxy with Monyog, click here.

23. Why is display of queries truncated in Query Analyzer?

A: When using Query Analyzer feature, you may notice that sometimes queries displayed in output are incomplete. This may be due to one of the three known causes:

  • The "Show partial" option is enabled, effectively truncating the queries displayed. This is changed by clicking on the "Show full" link at the head of the query column in the output table.
  • As a security measure, Monyog extracts only the first 2000 characters of the query.
  • MySQL does not record query delimiters in the General Log. Therefore, while analyzing the General Log, Monyog takes into consideration only the first line of the queries, and ignores the rest if they span over multiple lines.

24. The servers that I have registered do not display. What is wrong?

A: When you REGISTER a server it will not automatically become SELECTED. Only SELECTED servers will display. If you have lots of MySQL servers you would probably not want to display them all at the same time. You can REGISTER all servers (and data will be collected from those by the Monyog service running) and SELECT/DESELECT whatever server you want to display at the moment.

image

25. Now, anybody will be able to connect to my Monyog server and retrieve details about MySQL servers.

A: Of course not! The Monyog authentication system will ensure that only those people that should have access have!.

26. I have the same server registered twice. Metrics are reported different. Why?

A: For every registered server Monyog collects data independently. That is also the case when a server has been registered twice. Even if they were registered at the same time and even if the chosen sample interval is the same too, the connection and the server will have some latency and data will not be retrieved simultaneously. For that reason Monyog may (or rather will) retrieve and store slightly different values for each connection. This is most visible in the 'Delta' timeframe and least visible in the 'Current/all' timeframe. For GROUPING with 'History/Trends' the difference for each GROUP will depend on the selected grouping interval. Due to laws of statistics the difference will be less the longer the time interval (theoretically/statistically they will converge more and more the closer time interval and/or the no. of samples comes to infinity). Practically, you will rarely need more than around 20 samples in a GROUP for the difference to be negligible.

27. Will it affect the performance of a server if Monyog connects to it?

A: It will practically not on real 'live' servers. The queries sent by Monyog use almost no resources. We do not query data stored on disk and what we do query is stored in memory on the server. However if you are testing Monyog using a server instance that does almost nothing else and if you retrieve data at very short intervals the impact of Monyog may be slightly observable. The special Processlist feature (unique) may take a little more resources if there are lots of processes/client threads running. But Monyog only sends queries related to this when the corresponding Monyog client interface (the Monyog 'processlist' page) is open. Switching to another page or closing the browser will stop sending the queries populating the Monyog processlist.

28. Is it possible to avoid that Monyog itself influences certain counters reported?

A: Monyog is a client. When it connects the MySQL server will start a connection thread. And that connection will be reported by Monyog. That cannot be avoided. The processlist feature has an option to 'filter out' Monyog connection - as well as other connections from other clients if you want - using a simple SELECT statement.

29. Can I customize Monyog counters?

A: Regarding customizing Monyog counters refer to Customization. For scripting examples refer Customization Scripting Examples.

30. I cannot sit watching a browser all the time - Can I get alerts if something goes wrong?

A: Yes, you can choose to get notifications (email and/or SNMP traps) independently for every server and you can define your own warning levels and select what counters should raise an alert.

31. Monyog cannot identify if destination of the log file is on a "Mapped Network Drive". Why?

A: By default Monyog service runs under Local System Account. If you are having Slow query or General query log in a Mapped Network Drive, Monyog will not be able to reach it. If Monyog has to access the file present in a Mapped Network Drive, you have to convert the path into shared path (accessed with UNC notation: \system\share) and then follow these steps:

  • Click on Start menu, then click on run and then type,

    services.msc
    
  • After this 'Services' window pops up with list of all services running in your system.

  • Search for Monyog and then right click --> Properties.
  • Click on "Log On" tab and then you can see that Monyog is using "Local System Account".
  • You need to use "This account" option and then give the credentials that you use to log on to the system with "Administrative" privilege.
  • Save the settings, restart Monyog service.
  • After following the above steps try to access the file which is shared across network.

Note

The shared path should be accessed with UNC notation (\system\share). Monyog cannot identify if destination of the log file is on a Mapped Network Drive (this is a restriction with services on Windows and not with Monyog).

32. Failed to connect to MySQL: Unknown MySQL server host... What can i do about this?

A: You get this error if Monyog cannot resolve the hostname of a MySQL server. Ensure that other programs like ping, telnet, MySQL shell client are able to resolve the hostname to an IP-address. If yes, check "/etc/nsswitch.conf" of Monyog host. If the hosts section reads "files mdns4_minimal [NOTFOUND=return] dns mdns4", please change it to "files mdns4_minimal dns mdns4" or "files dns". This is introduced in some current Linux distribution. If other programs are not able to resolve the hostname, please check if host to ip resolution is properly defined inside "/etc/host" or in DNS server.

33. How can I monitor the queries from the file based RDS/Aurora Query logs?

A: Monyog can fetch the queries from the Slow Query log and General query log on Amazon RDS instance using the RDS REST APIs. Monyog requires the AWS access keys to fetch the file-based logs. Go to the Edit Server->Advanced->MySQL Query log and enable the option of "Monitor MySQL Query Log". Click on the Fetch logs(down arrow) button and provide the AWS access key and secret access key to enable Monyog to monitor the log files.

image

34. What are future plans for Monyog?

A: Monyog is an important product for us. We plan to add new features as well as to 'refine' existing features. With the latest 3.1 release we have completed what we originally planned for Monyog (and a little more actually).

  • Most Intrusive feature "Customization of Monyog counters"

  • Basic LAMP monitoring (Apache webserver and PHP metrics)

These features have all been requested by users. Monyog development has always been and will continue to be very attentive to user requests. We will update information here when plans for future developments have been decided.

35. How do I get help and report problems?

A: Two ways,

Website http://www.webyog.com

Post in our Forums http://www.webyog.com/forums

36. Can I use the keys generated from PuTTY for SSH connection?

A: Monyog does not support the key generated from PuTTY for SSH connection. However, there is a workaround for it that you can use, you can convert the private key generated from "PuTTY key generator" into an open SSH key, and then you can use this key in Monyog to connect to the server. Here are the steps to follow:

  • Go to PuTTY key generator, and generate a public/private key on your local system (refer the screenshot). Click on the Generate button to generate the keys.

image

  • Copy the public key generated under the "Key" space to the authorized_keys file, which is located in the .ssh directory on the remote host that you want to connect to.
  • Go to "Conversions" in PuTTY key generator and click on "Export openssh key" and save the new converted private key in a file.
  • Now open the file containing the converted OpenSSH private key, copy this key and paste in the "Private key" field in Monyog (Edit server -> SSH settings -> Private key).

37. Steps to auto-start Monyog service with OS reboot in Ubuntu and Debian systems.

A: Users can make use of the "MONyog" script shipped with the Monyog package to auto-start Monyog service with OS reboot. The MONyog script is located at " /MONyog/bin/". Please follow the below steps:

  • Copy the 'Monyog' to "/etc/init.d/" from " /MONyog/bin/"
  • Open the 'Monyog' script located at "/etc/init.d/" and edit the variable "curdir" (line number 15) and set it to the path of bin. After editing, it should look like this: curdir="/home/Users/Downloads/MONyog/bin/"
  • Make the script executable by 'chmod +x /etc/init.d/MONyog'
  • Use debian utility update-rc.d to install the script: update- rc .d MONyog defaults

38. How to upgrade Monyog without losing your data or configuration?

A: The Monyog binaries are shipped in 3 packages: .tar, .rpm and .exe. The upgrade process is simple and depends on your package. The below steps will help you upgrade to the latest Monyog version without a hassle:

For .rpm package :

  rpm -Uvh <Monyog_package>.rpm

This command will install the latest build on top of your current installation.

For .tar package:

  tar -xzvf <Monyog_package>.tar.gz

Please untar the package in the directory where the ‘MONyog’ package was untarred for the previous version to make sure that all your data and settings are intact.

For Windows (.exe) package:

Executing the file will install Monyog on top of the current installation.

All Monyog data and the configuration files are stored in an SQLite repository. In some of the Monyog GA releases, we modify/change the monitor definition in the SQLite files due to some bug or enhancements. In such cases, on upgrading, all the local changes made by the user in the previous version gets replaced with the default shipped value and these local changes are shown as a conflict. You can see the conflicts as a notification on the top right-hand corner.

To resolve conflict

You can resolve these conflicts from the “Settings -> Manage changes” page, herein you get 2 options for all the listed conflicts: Use your changes/Discard your changes. 1- Use your changes will restore the local modifications which you had made in the previous version. 2- Discard your changes, will replace your changes with the default values.