Once the runtime entity has been launched (or the launch has failed), the Executor sends back a status message on the `LOG_COMMON` topic.
```javascript
{
"message_type":"deployment_launch",
"message_type":"deployment",
"reason":"launch"/"terminate",
"node_id":"unique-machine-id",
"entity_id":"handle for the actual container/VM/etc.",
"entity_type":"docker/libvirt/etc.",
"resource_id":"logical-entity-id",
"function_id":"unique-function-id",
"timestamp":"time(2) compatible timestamp",
"reason":"deployment"/"termination"
"status":true/false// Only valid if reason==deployment
}
```
Instrumentation data is also sent on the `LOG_COMMON` topic. This data is sent from whichever part of the pipeline has access to the relevant information,
and whoever needs the data is allowed to read it. Each message is required to have atleast three fields: `node_id`, `resource_id` and `function_id`.
```javascript
{// From Docker
"message_type":"instrumentation",
"node_id":"unique-machine-id",
"resource_id":"logical-entity-id",
"function_id":"unique-function-id",
"entity_id":"handle for the actual container/VM/etc.",