Page History
...
Check if the server is filtered based on a particular state, change your server filter to All Servers and now you will be able to see your server amongst between the servers if you had successfully registered it. You can also use the search bar next to the server filter to search for your server name or tag name to get to your server.
...
For every registered server SQL DM for MySQL collects data independently. That is also the case when a server has been registered twice. Even if they were registered at the same time and even if the chosen sample interval is the same too, the connection and the server will have some latency and data will is not be retrieved simultaneously. For that reason SQL DM for MySQL may (or rather will) retrieve and store slightly different values for each connection. This is most visible in the 'Delta' timeframe and least visible in the 'Current/all' timeframe. For GROUPING with 'History/Trends' the difference for each GROUP will depend depends on the selected grouping interval. Due to laws of statistics the difference will be is less the longer the time interval (theoretically/statistically they will converge more and more the closer time interval and/or the no. number of samples comes to infinity). Practically, you will rarely need more than around 20 samples in a GROUP for the difference to be negligible.
| Anchor | ||||
|---|---|---|---|---|
|
27.
...
Does it affect the performance of a server if SQL DM for MySQL connects to it?
It will practically does not affect on real 'live' servers. The queries sent by SQL DM for MySQL use almost no resources. We do not query data stored on disk and what we do query is stored in memory on the server. However if you are testing SQL DM for MySQL using a server instance that does almost nothing else and if you retrieve data at very short intervals the impact of SQL DM for MySQL may be slightly observable. The special Processlist feature (unique) may take a little more resources if there are lots of processes/client threads running. But SQL DM for MySQL only sends queries related to this when the corresponding SQL DM for MySQL client interface (the SQL DM for MySQL 'processlist' page) is open. Switching to another page or closing the browser will stop stops sending the queries populating the SQL DM for MySQL processlist.
...
SQL DM for MySQL is a client. When it connects, the MySQL server will start starts a connection thread. And that connection will be is reported by SQL DM for MySQL. That cannot be avoided. The processlist feature has an option to 'filter out' SQL DM for MySQL connection - as well as other connections from other clients if you want - using a simple SELECT statement.
...
By default MONyog(SQL DM for MySQL) service runs under Local System Account. If you are having Slow query or General query log in a Mapped Network Drive, SQL DM for MySQL will is not be able to reach it. If SQL DM for MySQL has to access the file present in a Mapped Network Drive, you have to convert the path into shared path (accessed with UNC notation: \system\share) and then follow these steps:
Click on the Start menu, then click on run Run and then type,
Code Block theme Confluence services.msc
- After this 'Services' window pops up with list of all services running in your system.
- Search for Monyog and then right click --> Properties.
- Click on "Log On" tab and then you can see that SQL DM for MySQL is using "Local System Account".
- You need to use "This account" option and then give the credentials that you use to log on to the system with "Administrative" privilege.
- Save the settings, restart MONyog(SQL DM for MySQL) service.
- After following the above steps try to access the file which is shared across network.
...