monitoring - transferring custom situations
firstname.lastname@example.org 100000R23X Visits (5637)
Most customers have multiple cloud group or multiple environment profiles with externally managed cloudgroups, – to segregate production from non-production instances, to support a cloud service for different departments, … - and within every cloud group, they provide some shared services.
It’s very likely they might even have created a so-called custom monitoring situation or a personal workspace. As these artifacts are not transferrable through the IBM PureApplication GUI, how can I get my favorite situation (i.e. monitor launching vi) and the workspace transferred from one of my cloud groups to the monitoring portal in the other cloud groups as a way to promote custom monitoring situation from within one environment to another, from non-production to production?
In this example we explain you how to export, delete and import a custom situation using the command line interface provided with the PureApplication monitoring shared service.
1) login to the monitoring server as the sysadmin OS level user (password set at service creation time):
2) go to /opt/IBM/ITMSS/bin and execute:
./tacmd login -s localhost -u sysadmin
and if you don’t add a password, you need to provide it at the prompt.
"KUIC00007I: User sysadmin logged into server on http
3) then issue:
If you don’t provide a path where the artifacts should be exported to, it’ll take the current working directory just make sure you have the rights to create a directory “Bulk” at the working location or the one you specified. If not, please make sure you export to a location where you have those rights.
"KUIBSE015I: All of the situations were successfully exported from the managed server at http
... and many more.
One of them being my situation:
By the way, IBM recommends to run these commands using the root user as this lifts potential issues with user rights and (file or directory) access.
Of course, if you are able to run those monitoring portal CLI commands remotely (from another instance), don’t forget to replace the localhost parameter.
Check out the available monitoring portal CLI commands:
What did we describe here?
Using the command line tools provided with the PureApplication Monitoring shared service Portal, a monitoring administrator can easily define monitoring situations in one cloud group and transfer these to another cloud group or to another PureApplication Monitoring shared service instance.