Bug #75756 mysqlmonitoragent install add to group in MEM console
Submitted: 3 Feb 2015 23:36 Modified: 4 Feb 2015 16:25
Reporter: brendan mccauley Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any

[3 Feb 2015 23:36] brendan mccauley
Description:
It would be nice if there was a switch to add the device to a group in the MEM console other than "all servers" when installing the agent

How to repeat:
run ./mysqlmonitoragent-*-installer.bin and the device is added to the all servers group in the mem console. it would be nice to have a cmd line switch when installing the agent to add it to another group.

Suggested fix:
example:
./mysqlmonitoragent-2.3.12.2174-linux-glibc2.3-x86-64bit-installer.bin --mode unattended --unattendedmodeui minimal --debuglevel 0 --mysqluser agent --mysqlpassword agent44 --createaccount 1 --agentuser user --agentpassword password --managerhost managementhost --add-to-group "nonprod"

the above example would run the installer with some options and add it to a group in the mem console named "nonprod"
[4 Feb 2015 0:09] Matthew Lord
Hi Brendan,

You should be able to achieve this using the following command-line option for the agent installer:
 --mysqlconnectiongroup <mysqlconnectiongroup>

http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-unattended-installation-cmdline-options-...

Was this not working as expected? Or perhaps you just missed it?

Thank you for the feedback!

Best Regards,

Matt
[4 Feb 2015 0:13] Mark Matthews
This feature already exists, use the --mysqlconnectiongroup flag with the unattended installer, see http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-unattended-installation-cmdline-options-...
[4 Feb 2015 0:27] Andy Bang
Just to make it clear, the add-to-group feature is in the MEM 3.0 Agent installer, but the original inquiry referenced MEM 2.3, which does not have it.
[4 Feb 2015 16:25] brendan mccauley
wow, you guys fixed that pretty fast! ;)
i thought i was looking at the 3.0 flags page but now it's clear that i was not (and hence, the flag was not listed there). thanks for setting me straight.