Description of problem:
Couldn't the hostname be included in a heartbeat event from to help distinguish between events?
Mon Aug 8 15:57:21 2011 INFO org.matahariproject:heartbeat broker=localhost:49000 timestamp=1312819041 sequence=40
Mon Aug 8 15:57:22 2011 INFO org.matahariproject:heartbeat broker=localhost:49000 timestamp=1312819042 sequence=588
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install an local matahari broker and host agent on serverA
2. Start broker and agent on serverA
3. run qpid-printevents on serverA, see heartbeat event from local host agent
4. Install host agent on serverB
5. configure host agent on serverB to connect to broker @ serverA
6. start host agent on serverB
7. see new heartbeat events in qpid-printevents from step 3, no way to distinguish between the events (besides the sequence which really will not work after running any amount of time)
Hardware UUID too
A related patch has been committed upstream: https://github.com/beekhof/matahari/commit/bfa436e
good 2 go in v0.4.2-6
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: The Host agent produces heartbeat events, but previously included only time related meta data.
Consequence: It was in some ways difficult to associate heartbeat events with the host they originated from. This was primarily the case in logs.
Change: The heatbeat events produced by the Host agent now include the hostname and the hardware UUID as additional meta data.
Result: It is easier to associate the Host agent heartbeat events with the host they originated from.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.