Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

With SQL DM for MySQL installed on your server, you can begin to configure systems and databases in your infrastructure for its use.

Use SQL DM for MySQL to monitor a server, only grant its user access to MySQL and then register the server through the Web UI.

MySQL Configuration

When you register a server with SQL DM for MySQL, it collects information and monitors the server's health through standard MySQL client connections. You need to configure a user account with the appropriate permissions on each MySQL server you want to monitor. Fully enabling SQL DM for MySQL requires that you grant SELECT, RELOAD, PROCESS, and SUPER to this user. You can use whatever username you find convenient, with the host set to the server hosting SQL DM for MySQL.

For instance, say you have installed SQL DM for MySQL on a server at 192.168.1.150 and that you would like use the user monyog as the user name. To fully enable SQL DM for MySQL in this scenario, you would issue the following command:

Code Block
themeConfluence
GRANT SELECT, RELOAD, PROCESS, SUPER ON *.*

TO 'monyog'@'192.168.1.150';

Granting these permissions makes the MySQL server fully accessible to SQL DM for MySQL. To actually start collecting data on this server you also need to register it with the application.

Running SQL DM for MySQL as unprivileged user

By default, SQL DM for MySQL runs under the 'root' account in Linux. This may be a security nightmare for some.

Here's how you can create and use a user account exclusively for running SQL DM for MySQL:

  • First add a new user and group; replace <GID>, with the group ID, and <PASSWORD>:
Code Block
themeConfluence
# groupadd monyog
Code Block
themeConfluence
# useradd -g <GID> -p <passwd> monyog
  • Copy the original files to the new location and change the file ownership.

Code Block
themeConfluence
# cp -r /usr/local/MONyog/. /home/monyog/
Code Block
themeConfluence
# chown -R monyog:monyog /home/monyog
  • Next, we need to change the initialization script. Be sure to make a backup first!

Code Block
themeConfluence
# cp /etc/init.d/MONyogd /etc/init.d/MONyogd.orig
Code Block
themeConfluence
# vi /etc/init.d/MONyogd
  • Change the following lines for the new path.

Code Block
themeConfluence
PREFIX="/home/monyog"
Code Block
themeConfluence
MONYOGBIN="$PREFIX/bin/MONyog"
  • In the same file, you also need to update the start command to the following.

Code Block
themeConfluence
# Start MONyog
...
else
action "`su - monyog -c \"$MONYOGBIN -s\"`" /bin/true
fi
  • Now you need to alter the configuration file.

Code Block
themeConfluence
# vi /home/monyog/MONyog.ini
  • Change the data path to the new directory.

Code Block
themeConfluence
Data_path=/home/monyog/data
  • After this you should be able to start SQL DM for MySQL running as an unprivileged user.

Code Block
themeConfluence
# service MONyog start



Scroll pdf ignore
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
| 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
| 

...

 

...

 

...

 

...

 

...

 

Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
|
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
|
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
|
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
|
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
|
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse

...