@Santosh, there is no issue in hostname, please check the setup.
as mentioned in comment #3, alarm was seen with name of compute1 instead compute2, now why this was seen even when agent was running on compute1(and stopped on compute2) this you can debug from the logs only as this is not seen again while debugging.
I think right now you can debug the issue from the perspective of alarm not at all getting generated.
@Santosh, there is no issue in hostname, please check the setup.
as mentioned in comment #3, alarm was seen with name of compute1 instead compute2, now why this was seen even when agent was running on compute1(and stopped on compute2) this you can debug from the logs only as this is not seen again while debugging.
I think right now you can debug the issue from the perspective of alarm not at all getting generated.