
|
If you were logged in you would be able to see more operations.
|
|
|
Hyperic HQ
Created: 17/Apr/08 08:44 AM
Updated: 28/Aug/08 04:44 PM
|
|
| Component/s: |
Server
|
| Affects Version/s: |
3.2.2
|
| Fix Version/s: |
4.0.0,
3.2.4
|
|
| Verify By: |
Kashyap Parikh
|
| Last comment: |
12 weeks ago
|
| Resolution Date: |
02/Jun/08 03:33 PM
|
|
Not sure if this only applies to platform resources, but the reproduction is this:
1. Configure an SNMP platform resource that contains some services (i.e. a Network Host/Device with some network interfaces)
2. Change the IP address of the host/device
3. Change the IP address in the HQ resource Configuration Properties
At this point, the metrics on the platform resource will begin collecting again using the new configuration, but the services like the network interfaces will still have the old configuration and will not be able to collect metrics.
Workaround: re-submit the config on each service by navigating to the Configuration Properties, clicking Edit, then Click OK without changing anything. That will force the update from the parent.
Expected behavior is that the service configuration is updated automatically when the parent resource configuration is changed.
|
|
Description
|
Not sure if this only applies to platform resources, but the reproduction is this:
1. Configure an SNMP platform resource that contains some services (i.e. a Network Host/Device with some network interfaces)
2. Change the IP address of the host/device
3. Change the IP address in the HQ resource Configuration Properties
At this point, the metrics on the platform resource will begin collecting again using the new configuration, but the services like the network interfaces will still have the old configuration and will not be able to collect metrics.
Workaround: re-submit the config on each service by navigating to the Configuration Properties, clicking Edit, then Click OK without changing anything. That will force the update from the parent.
Expected behavior is that the service configuration is updated automatically when the parent resource configuration is changed. |
Show » |
|
Another work around for this problem is to refresh the agent schedule on the agent which monitors these resources:
./hq-agent.sh stop
rm -rf data
./hq-agent.sh start