Message Schema Specification
Currently, the message formats that are published and consumed by Monasca have been developed for internal use only. The messages are in a JSON format that was largely developed without a lot of consideration for supporting external or third-party components, applications and services. While the current message format is OK for internal and easy to by external applications, there is a risk to them in doing so.
Consequently, we are in the process of reviewing the messages used by Monasca and creating a formal message schema specification that is used by Monasca, such that external third-party components, applications and services outside of the Monasca system can easily publish and consume from the MessageQ without being concerned about future changes. We plan to define the message schema and treat it as an external specification such that third-parties can work with Monasca without being concerned about future changes. One use case for doing this involve enabling third-party data analytics applications.
Blueprint information
- Status:
- Not started
- Approver:
- Roland Hochmuth
- Priority:
- Undefined
- Drafter:
- Roland Hochmuth
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- Accepted for trunk
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by