Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: Slow Query Log Analyzer #30716

    The “Export As CSV” option eats up all the CPU and never finishes when we do a sort on any column (say count) and then click Export. And I cannot stop MonYog service too when this happens. It fails.

    The slow query log analyzer is such a good and important feature in MonYog but cannot be used effectively because of its limitations mentioned in this thread.

    I am attaching a screen shot of the cpu/memory usage by MonYog at the time of doing this operation for your reference. And the cpu usage never drops after this.

    Ratheesh

    in reply to: Slow Query Log Analyzer #30714

    Hi Sandhya,

    Is there any future plans to show all records (may be using pagination). Or at least to export all records into CSV. Because in a production environment where we want to generate a report of slow queries for a whole month, the top 200 records will just list for the ast 5 or 6 days.

    This is a very good feature to have.

    'sandhya.r' wrote on '30:

    Hi,

    As per design MONyog will display only the top 200 records in the Query analyzer page.

    Sorting the result causes the sort algorithm to be applied to the entire table but only the top 200 rows are displayed.

    Regards,

    Sandhya

    in reply to: Explain Query Fails #30473
    'sandhya.r' wrote on '08:

    Hi,

    Issue is confirmed.

    Thanks for reporting the bug. We will have it fixed in the next release of MONyog.

    Regards,

    Sandhya

    Hi Sandhya,

    Can you let me know which is the next release of Monyog and when it is expected?

    Ratheesh

    in reply to: Not Getting The Email Alerts #30071
    'Sayan wrote on '30:

    Hi Ratheesh,

    For 'Percentage of Full Table Scans' to be reported correctly, the MySQL server should be running for some time, ie, the server has to warm-up. By default, MONyog sets this warm-up time to 3 hours (which can be changed from Tools –> Preferences). So, only after MySQL has been running for 3 hours, MONyog considers that counter's value for alerting.

    Can you find out your MySQL server's uptime (from 'General Info' –> 'Running For' in the Monitors/Advisors page), and get back to us here?

    Hi Sayan,

    I had already changed the “Warm Up Required” parameter to No before setting up the alert. Anyways I got a delayed alert. But I am not getting how the alerts are functioning. Do you have any idea? I have set the alert-able to 1. What does that mean?

    Ratheesh

Viewing 4 posts - 1 through 4 (of 4 total)