Description of problem: It would probably less confusing to users to change the default entry here from 127.0.0.1 (loopback) to the resources real hostname or ip. The ip that is sent in alerts will be changed from es> Alert -- test01 (on 10-16-120-153.guest.rhq.lab.eng.bos.redhat.com RHQ Agent): http://localhost:7080/alerts/Alerts.do?mode=viewAlert&id=10002&a=10011 to: Alert -- test01 (on 10-16-120-153.guest.rhq.lab.eng.bos.redhat.com RHQ Agent): http://10.16.120.153:7080/alerts/Alerts.do?mode=viewAlert&id=10002&a=10071 Administration -> Server Configuration -> Settings RHQ General Configuration Properties GUI Console URL: Thank you!
content = content.replaceAll("@@@BASEURL@@@", "http://" + ServerProperties.getValidServerBindAddress(props) + ":" + ServerProperties.getHttpPort(props) + "/"); That is code inside the installer war - the installer will set the default value in the DB using that code above - i.e. the server bind address. Perhaps we should use a different default here? Note that this will only take effect when you do a "Overwrite Schema" - because that @@@BASEURL@@@ is a replacement string inside the sysconfig-data.xml file that is used to prepopulate the database when the schema is first created. Adding more servers to the cloud or re-installing the server with the "Keep Existing Data" option won't change this value. This base url is the value you see in the UI in Administration>SystemConfiguration>Settings.
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage