Forum Replies Created
June 24, 2014 at 1:14 pm in reply to: Installing And Securing Monyog – Production Environment #34994
1) Can we install MONyog ON mysql ? Because we want backup MONyog environment for security and to have historical data secure.
–> MONyog can be installed on machine where MySQL is installed or on remote machine , MONyog uses TCP/IP connection to connect to the MySQL server.
2) How should look like production implementation of MONyog ? Enviremont backup etc.
–> Can you please elaborate?
MONyog stores all embedded data in /MONyog/data/ directory
Please refer this FAQ on “Where does MONyog stores it’s data”
Please let us know if you need any help.
Team MONyogMay 26, 2014 at 6:06 am in reply to: #34763
Using MONyog it’s not possible to add or remove a node on Galera cluster. There is a tool from MariaDB can be useful in this case. https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/
We will discuss on this feature request in our team meeting and get back to you.
You should use just “-f” option instead of “-x” option, it will work.
“man” page for “pkill” explains that:
“-f” :- The pattern is normally only matched against the process name. When -f is set, the full command line is used.
“-x” :- Only match processes whose name (or command line if -f is specified) exactly match the pattern.
Team MONyogApril 25, 2014 at 4:44 am in reply to: #34890
We have fixed this issue in v5.72 GA now you will not get notification for “gtid_executed” and “gtid_owned” variable.April 25, 2014 at 4:42 am in reply to: #34894
MONyog sends email alert only if monitor value changes from “stable” to “alert” state. It will not send another email alert until monitor value changes from “alert” to “stable” and again from “stable” to “alert”.
We are alerting to make sure that you should pay attention to it and avoid the problem, frequently sending email alert for same monitor also considered as a “SPAM” and you will not pay attention to it.
In “Edit server ” –> “Notification settings”
* You can see “Send notification when alert-able” by default this value is “5” you can change it to “1” to get immediate notification.
* Also you can see “Notify when stable” option you should check this option to get “Stable” email notification as well
Team MONyogApril 25, 2014 at 4:33 am in reply to: Queries Under 1 Second Not Showing Up In The Real Time Montior. #34902
“Real-Time” currently shows only queries which takes more than 1 second as it executes “Show Full Processlist” query in the background every second and captures the queries.
We are planning to implement P_S based “Real-Time” which won’t skip any query, provided that you should be using MySQL v5.6+
This is a known issue with MONyog. In this case for “Locked” and “Locking” queries it considers MySQL server Timezone whereas for queries tab it considers MONyog’s timezone and hence there is a difference in time.
We will look into this issue after current important tasks at hand.April 10, 2014 at 5:30 am in reply to: #34889
We will fix this issue for `gtid_executed` variable as well as other system variables which changes their values.March 28, 2014 at 10:18 am in reply to: #34851
Sorry for being late in reply.
We have tried by creating a prepared statement and executed it using execute prepare statement but still PROCESSLIST does not show “Command” column as “Prepare” or “Execute”. We have asked in stackoverflow as well but no one has replied yet
If possible can you zip and attach sample query, table strucure with sample data ?
specify MySQL server version as well.
MaheshMarch 20, 2014 at 4:26 am in reply to: #34849
Difference between Cumulative and Point-in-time counters
Cumulative Metrics’ (that increase with time and can be recorded for a period (like ‘Key_reads’, ‘Maximum no. of Connections that Ever Was’) are calculated differently instead of point-in-time metrics (like ‘Server Availability’, ‘Currently Running Threads’).
For ‘cumulative metrics’, MONyog will send alerts if thresholds are crossed for last collection interval.
For ‘point-in-time’ metrics, MONyog will send alert only based on ‘Current’ values (for instance current no. of connections is close to Max Allowed Connections – there is nothing more to consider!)
Let me explain with an example:
In Current connections group a monitor called “Max Allowed” is non cumulative value and hence you can see property “Uptime” set to “No” (Click on a monitor –> Customize –> View advanced –> scroll down and see “Uptime” property is set to “No”)
In Connection history group a monitor called “Refused” or “Percentage of refused connection” is a cumulative value and hence property “Uptime” is set to “Yes”.
These values are based on particular monitor and you have to decide which is uptime based and which is not, basically all Status variables are Uptime based monitors as their value increases with time server started.March 19, 2014 at 11:19 am in reply to: #34850
We will check this and update the status.March 19, 2014 at 3:18 am in reply to: #34847
Let me explain you in detail:
1) MONyog collects data by executing “Show Variables;” and “Show Status;” statement on a server at every interval specified in “Advanced settings” –> “Data collection interval” (Default is 5 minutes). If there is any critical event like “Hacking attempts”, “MySQL server is down” etc… then it sends a notification email based on delta values (difference in values between last two data collection)
2) You can verify yourself by executing these queries at data collection specified in MONyog (assume every 5 minute) and calculate the difference between values and verify against MONyog, values has to be approximately same.
In summary, MONyog considers delta (difference in values between last two collection) to send notification email.March 6, 2014 at 1:39 pm in reply to: #34822
We have tried against MySQL v5.5.33 and we are getting proper count for a store procedure. MySQL server decides whether to use store procedure name or queries inside store procedure.
You can check yourself “Show Full Processlist;” output to verify whether queries or store procedure name is shown.
You can change filter option in “Query Analyzer” page (you can see `change filter` link where you can specify Timeframe to analyze data like 1 hour, 2 hour etc.. )March 6, 2014 at 1:35 pm in reply to: #34829
This is for MySQL server restart. We have checked against v5.69 and it works fine, refer attached screenshot