- Rationale
The BPMN Monitoring has been defined as a pain point since the Amsterdam release. Camunda cockpit regardless community or enterprise editions were designed from a BPMN process management perspective. Camunda is not an OSS vendor, and they don’t have a reason to cover service-level monitoring. As a result, it does not meet service-level orchestration monitoring from the OSS perspective.
- Search is an Camunda enterprise feature, but we need to provide searching capabilitiy capability for non-enterprise edition.
- Finding right process instance(s) for a NS/VNF service request is tedious and hassle.
- To facilitate monitoring, we need more than what Camunda Community/Enterprise edition supports.
- provides the process monitoring (instance-search) hyperlink to the SO clients for launching process monitoring.
- Automates tedious manual steps for finding target process instance(s), bypassing tedious search starting from the process defintions.
- Access customized SO Monitoring Service List (or Camunda Cockpit widgets) from VID, UUI and external API users.
- If a service provider uses Camunda Enterprise edition, they can still utilize this SO monitoring on top of Camunda enterprise edition features.
- Many of Camunda enterprise features such as CRUDV and version control of process definitions would be part of SDC.
- ONAP separated workflow design and runtime.
- Several enterprise features are not part of SO monitoring features and are not applicable.
- What are current TOSCA orchestrator monitoring capabilities?
- SO monitoring should cover both imperative and declarative orchestration.
- Question: can we have a kind of uniform way of monitoring?
...