Page History

...

1. Please check whether you have libxml2 installed in your system.
2. Download mod_proxy_html.c from from 

   Newtab2
   alias http://apache.webthing.com/ url 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].

   Code Block
   theme Confluence
   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]

...

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. However, important differences are:

• SQL DM for MySQL 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.SQL DM for MySQL needs no installation (of 'agents') on the server where the MySQL servers are running. Other does.
• SQL DM for MySQL '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 SQL DM for MySQL. Download packages and disk storage required are much smaller with SQL DM for MySQL.

...

20. SQL DM for MySQL throws an error when trying to connect to MySQL.

Please go through through 

...

You may have noticed that, while using the PROCESSLIST-based sniffer, SQL DM for MySQL 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. Do not panic: it is normal. When using the PROCESSLIST-based sniffer, SQL DM for MySQL continually queries the MySQL server at the end of each time interval, which you can specify. 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 short time interval, one that almost approaches 0, then SQL DM for MySQL can get stuck in an infinite loop! Consequently, the load on the CPU and I/O subsystem increases exponentially. We generally recommend an interval of not more than 0.1 seconds times the number of servers for which Processlist-based sniffers are enabled. However, if you are worried that you may miss out on some important queries running on the MySQL server, use the Performance Schem or MySQL Proxy mode. The LUA script supplied with SQL DM for MySQL should handle the task for MySQL proxy. For more information on using MySQL Proxy with SQL DM for MySQL, click herereview

TOP

Anchor
FAQ-23 FAQ-23

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

...

Four ways:

• Website Intercom 

  Newtab2
  alias https://www.idera.com/ url https://www.idera.com/

• Post in our Forums Forums 

  Newtab2
  alias http://community.idera.com/ url http://community.idera.com/

• Create ticket: ideramysqlsupport@idera.com
• SQL DM for MySQL UI intercom

...

sudo monit reload

TOP