[Mahesh]

Hello,

1) Try with this URL http://127.0.0.1:5555 OR http://:5555 (5555 is a default port, if you have changed this port, specify that port)

2) Could you please check if the MONyog service is running?

3) Check firewall settings, 5555 port should be open.

4) Try installing MONyog again?

5) MONyog version and details of machine where MONyog is installed will be helpful as well

Regards,

Team MONyog

[Mahesh]

Hello,

• MONyog monitors your MySQL server as soon as you have registered/added it, You can see statistics about your server on Monitors, Dashboard page. MONyog collects data from server every 5 minutes (Default collection interval) and incase if there is any critical events like MYSQL server is down, Replication slave is not running, Slave is lagging behind master, High CPU usage etc.. happens it alerts you by sending an email or via SNMP trap, you can configure Mail settings and SNMP settings from Tools. MONyog also gives historical statistics about Monitors (Goto Monitors Page –> Select `History` from Toolbar –> select a monitor for which you want to get historical data)

• You can use Query Analyzer to analyse queries executed on your server by using any of this method:

1) Slow log analysis, you can specify your slow log file details by (Edit server –> Advanced settings –> Query log details)

2) Similarly General log analysis

3) Sniffer- Sniffer has two modes Via Processlist and via MySQL proxy

Processlist – Processlist based sniffer executes `Show Full Processlist;` every 1 second and analyse queries

MySQL Proxy – You can configure MySQL proxy and route your application to connect to Proxy, MONyog connects to proxy and analyse queries executed.

Sniffer output can be viewed in WayBack Machine tab also as it uses Sniffer data to show query details.

• Real-Time is what you need to use if you do not have Slow log or sniffer and still want to know what is happening on your server in real time. It continuously executes a bunch of queries on a server and fetches information on the top queries, tables, databases, user, hosts, queries that are locked, queries that are locking etc…When Real-Time session is in progress and you want to switch to other tab .. MONyog prompts “Your data will be lost … ” this confirmation message is intentional if a user wants to save running session for analysis he can save otherwise discard it if it's not useful for analysis.

For example: You are observing a load on your server at specific time everyday between 1-2 PM you can start Real-Time session at this time today and save the session and after optimizing queries, table structure you can compare it tomorrow at same time to see performance gain for problematic queries.

• WayBack Machine shows a message “Populating queries may take sometime. To start populating click here” this message will appear if there are more than 2000 queries in a selected timeframe and this is just to inform analysis may take few minutes.

• If you logout from MONyog interface still MONyog continues to collect data in the background but if there is any Real-Time session running that will be discarded.

Please let us know if you need any help, you may also create a support ticket by sending email to `[email protected]`

Regards,

Team MONyog

[Mahesh]

Hello,

1) Make sure that MySQL user registered with MONyog has SELECT privilege for `mysql`.`user` table.

2) Paste the output of this query:

Show grants for `monyog_user`@'host';

Note: MONyog user will need SELECT privilege to the `mysql`.`users` table. Additionally, if the server was started with the 'skip_show_databases' option, you must explicitly grant SHOW DATABASES privilege for MONyog security counters to be functional.

[Mahesh]

We have added EXPLAIN plan for Insert, Update and Delete for MySQL server 5.6+ in Processlist page as well

http://blog.webyog.com/2013/11/28/monyog-mysql-monitor-5-66-has-been-released/

[Mahesh]

I guess you are talking about Processlist page where EXPLAIN icon does not appear for Insert/Update for MySQL v5.6,

MONyog shows EXPLAIN plan for Insert/Update queries in Real-time and we will implement this in Processlist page as well.

[Mahesh]

You can also click on `CPU usage` monitor from Monitors page –> Click on Customize — Value.

(please refer attached screenshot)

[Mahesh]

Joe,

CPU usage has been calculated by:

100 – (cpu_idle/total_cpu)

Where total_cpu is calculated by:

cpu_user + cpu_nice + cpu_system + cpu_idle + cpu_iowait + cpu_hi + cpu_si

[Mahesh]

Hello,

MONyog gets CPU information from /proc/stat and calculates and shows output.

/proc/stat output has been explained here:

http://www.linuxhowtos.org/System/procstat.htm

Regards,

Team MONyog

[Mahesh]

Hello,

Load Average as exposed by the Linux kernel in /proc/loadavg is available in Linux Group since MONyog v5.3,

You can upgrade to latest MONyog GA and check yourself.

Regards,

Team MONyog

[Mahesh]

We need these information to debug this issue:

1) Attach a screenshot of `LDAP settings` in MONyog (Goto Tools –> Ldap settings)

2) Attach screenshot of `user` added as LDAP in MONyog (Goto Tools –> User Manager)

3) Attach a screenshot of xWIKI configuration where it shows successful LDAP settings

[Mahesh]

We have already replied here http://issueburner.com/#issue_detail?issue_id=198939

Please continue discussion on this ticket http://issueburner.com/#issue_detail?issue_id=198939

[Mahesh]

Can you please tell us these information to debug this issue:

i) What kind of setup/environment you have in Amazon RDS?

1) Both master and Slave are running as RDS instance

2) Whether are you using Read replica feature of Amazon RDS?

3) Make sure that slave server is marked as YES in `Advanced settings` –> `Replication` section of MONyog while registering a server.

You can edit slave server and change it, and finally click on `Save All`

ii) Execute `show slave status` on RDS slave, what does it returns?

[Mahesh]

Quote:

[5.61] [2013-08-26 17:29:04] [Server: plcddbps1101 3306] srcymysql.cpp(507) ErrCode:1135 ErrMsg:Can't create a new thread (errno 11); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug

This is a MySQL error

It is possible that mysqld could use up to key_buffer_size + (read_buffer_size +

sort_buffer_size)*max_connections

You should reduce these values in line with the performance you require such that they do not

exceed the maximum amount of memory available. Remember that your OS and other

processes will require memory too.

You should report to MySQL bugs or discuss this error in MySQL forum.

Quote:

The monyog process is currently using 116,200k of memory and the server has 131gb of ram installed.

MONyog just uses 113 MB of RAM out of 131GB RAM so .. I don't think MONyog process has any issue with this.

[Mahesh]

After installation of MONyog … you can copy and paste all MySQL server's embedded data in `MONyog/data/` folder. You can also copy `MONyog.ini` file and preferences.config file to restore preferences.

If you need any help please create a support ticket by sending mail to '[email protected]'

[Mahesh]

Are you talking about MONyog- MySQL Monitor or SQLyog- MySQL GUI?

[Author]

Posts