C2MS11 — C2CX Heartbeat comments

(C2CX Heartbeat) Section 8.5.4

• Suggest not having CPU / Memory utilization in the messages. That would be better implemented through normal system monitoring mechanisms (e.g., SNMP). Code to retrieve such information is typically platform-specific and is not related to the business logic of the component.
• If such information is required, suggest having a system monitoring component instead.
• Unclear exactly how this would work in a clustered environment. Different hosts implementing the same service would provide conflicting answers.
• Unclear why the commentary on why memory leaks are bad is in the spec

Field and Text Changes to Heartbeat Message

Following changes to be made:

1. Remove CPU / Memory utilization in the messages
2. Replace Heartbeat Message Diagram
3. Remove text about memory leaks

See C2MS11-2 for rationale.

See attachments for original and revised figure, Figure 8-11. Heartbeat Message Diagram

Note: There had been discussion about whether it would be OK to remove fields from the spec. At a 2022 C2MS RTF Meeting, Jay was good with removing the fields.