-
Key: C2MS-9
-
Status: closed
-
Source: NASA ( Mr. John Bugenhagen)
-
Summary:
(C2CX Heartbeat) Section 7.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
-
Reported: C2MS 1.0a1 — Mon, 10 Sep 2018 19:21 GMT
-
Disposition: Deferred — C2MS 1.0
-
Disposition Summary:
Not necessary for now - fields are optional
Referenced fields in HB are optional, so not necessary to use them. And others have indicated the comment re: memory leaks is useful. SDTF Ottawa recommended deferring until next update cycle, i.e., Ver 1.1.
-
Updated: Fri, 3 Jan 2020 20:50 GMT
C2MS — C2CX Heartbeat comments
- Key: C2MS-9
- OMG Task Force: Command and Control Message Specification (C2MS) 1.0 FTF