[pankajk1608]

You can add a rule in your NAT/Proxy configuration which allows the static slack webhook for alerting.

Regards,
Pankaj

[pankajk1608]

Since you have already tried out the most probable way to find the issue behind this, maybe you can give a try to the solution provided in the link here >> https://www.percona.com/blog/2008/08/23/how-to-track-down-the-source-of-aborted_connects/

[pankajk1608]

Hello Palash,

 

Can you please send us the screenshot of the Monitors tab for the replication group, and also send us the screenshot if you are getting any console error on the page. Right click any where on the monitors tab -> inspect element -> console -> send us the screenshot if you have any error logged. Please send us the MONyog.log file, or better create a ticket at “[email protected]” and attach the log file, and will take it forward from there.

 

Regards,

Pankaj

[pankajk1608]

Hello Palash,

 

The query used by you is “show status like ‘slave%'”; which will give a different output than “SHOW SLAVE STATUS”. We use the query “SHOW SLAVE STATUS” on the slave server to fetch all the replication related data and display it in the Monitors tab. Please let us know if you are getting values for the counters in MONyog in the replication tab, which uses the query “SHOW SLAVE STATUS”.

 

Regards,

Pankaj

[pankajk1608]

Hello,

 

We are aware about the broken link for “MySQL Proxy”, we will be fixing this with the correct link in our next release.

 

Regards,

Pankaj

Team MONyog.

[pankajk1608]

Hello,

 

@jadn012, sure..we will add this fix in our next GA release.

 

@anup_fc, please create a ticket at [email protected], and we will provide you with a special build there with this issue fixed. I think you are using 64 bit rpm package, please confirm and we will provide you the build.

 

Regards,

Pankaj

Team MONyog

[pankajk1608]

Hello,

 

We have identified the issue, and it is because of the changes brought in the XML code for  REST API by AWS. We will fix this issue and will provide you with a special build. Please tell us which mode you used for MONyog installation, i.e, .rpm, .tar or .exe and also the architecture, i.e, 32 or 64 bits. Also, please create a ticket at [email protected] so that we could provide you the special build.

 

Regards,

Pankaj

Team MONyog.

[pankajk1608]

Hello,

 

The counter “Percentage of full table scan” gives the percentage of tables accessed by full table scans, i.e, when the data was fetched without using any index. A high value like 95-98% for this counter indicates that you are not using indexes for accessing the tables resulting into full scans. If your table size is huge, then this value can be critical as it would be taking longer time to fetch data, resulting into degrading your server performance. It is always recommended to use indexes to improve query execution time while fetching/Querying data, so use of indexes will help you bring down the high percentage value for this counter.

 

You can use slow-query-log with the option “log-queries-not-using-indexes” enabled to find the queries which are not using indexes, once you have identified the queries, you can create the appropriate indexes or rewrite the queries to use indexes.

 

 

 

Regards,

Pankaj

Team MONyog. 

[pankajk1608]

Hello,

 

We do not recommend downgrading MONyog to an older version as it may raise issues because of the changes made in the newer SQLite schema (which may have been brought for adding features, increasing performance etc.)

 

If you are asking for the older version, because of the “Processlist view” fixed height, then I would like to add here that we have fixed this issue, and now we will be providing the option to the user whether they want a ‘Fixed’ or ‘Dynamic’ processlist height. This change will be made public in our next GA release which is scheduled to release next week. Please reply if you still have any issue.

 

 

Regards,

Pankaj

Team MONyog.

[pankajk1608]

Hello,

 

You can use the MONyog API for this purpose. You can disable the alerts by firing an API at 1 am and enable it again at 3 am. Here are the APIs:

 

To disable alerts: curl “http://192.168.1.1:5555/?_object=MONyogAPI&_action=Alerts&_value=disable&_user=admin&_password=Password&_server=Production001″

 

To enable alerts: curl “http://192.168.1.1:5555/?_object=MONyogAPI&_action=Alerts&_value=enable&_user=admin&_password=Password&_server=Production001″

 

You can refer to our documentation here >> http://monyogkb.webyog.com/article/118-using-the-monyog-api

 

 

Regards,

Pankaj

Team MONyog.

[pankajk1608]

Hello,

 

This issue is reproducible at our end as well. We are working on it and will provide you a special build of MONyog, can you please create a support ticket at [email protected].

 

Regards,

Pankaj

Team MONyog.

[pankajk1608]

Hello,

 

We have added your request in our wishlist, the priority for it is not decided though.

 

 

Regards,

Pankaj

Team MONyog.

[pankajk1608]

Hello,

 

We will check this issue pertaining to API, can you please create a support ticket at [email protected] and we will carry on there.

 

Regards,

Pankaj

Team MONyog.

[pankajk1608]

Hello,

 

You will have to change the path from the MySQL configuration file. You can refer to MySQL documentation on how to enable error and slow query log and also to set a path for it here >> http://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html,  http://dev.mysql.com/doc/refman/5.7/en/error-log.html

 

After setting up the path, you just need to click on “Fetch” (Edit server -> Advanced settings -> MySQL error log) button and MONyog will fetch the path specified in the configuration file and display the content of the log files.

 

Regards,

Pankaj

Team MONyog.

[pankajk1608]

Hello,

 

There is an option in “Edit server -> Notification settings” as “Send notification when alert-able” wherein you can give integer values like 2, 3 etc, which means that MONyog will send you alerts only when a counter is in alert-able state for this (2,3 etc.) many data collection interval times consecutively, this setting is server level, meaning it will be applicable for all the counters and monitors.

 

The “Override send notification when alertable?” is a monitor level setting, and is used to override the value that you set for in the “Send notification when alert-able” option. So, if you have set up a value as 3 for “Send notification when alert-able”, then you can override this using the option “Override send notification when alertable?” for any monitor, if you want to get an alert for a lesser number of intervals for that monitor.

 

The value for this totally depends on your need, you can set a value 1, if you want to have an alert the first time counter gets into a critical condition or any higher value if you think the counter is not critical enough to look into if it is alert-able only for one data collection interval.

 

Regards,

Pankaj

Team MONyog.

[Author]

Posts