Skip to content

X
xanadu
Commit 5a5cae29 authored by Naman Dixit's avatar Naman Dixit
Browse files
Options

Changed log message format

parent f91589fa
Hide whitespace changes
Inline Side-by-side
Showing with 10 additions and 4 deletions
readme.md
View file @ 5a5cae29
...@@ -44,7 +44,10 @@ Format: ...@@ -44,7 +44,10 @@ Format:
Once the runtime entity has been launched (or the launch has failed), the Executor sends back a status message on the `LOG_COMMON` topic. 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 ```javascript
{ {
"node_id" : "uique-machine-id", "message_type" : "deployment_launch",
"node_id" : "unique-machine-id",
"entity_id" : "handle for the actual container/VM/etc.",
"entity_type" : "docker/libvirt/etc.",
"resource_id": "logical-entity-id", "resource_id": "logical-entity-id",
"function_id": "unique-function-id", "function_id": "unique-function-id",
"timestamp" : "time(2) compatible timestamp", "timestamp" : "time(2) compatible timestamp",
...@@ -57,7 +60,8 @@ Instrumentation data is also sent on the `LOG_COMMON` topic. This data is sent f ...@@ -57,7 +60,8 @@ Instrumentation data is also sent on the `LOG_COMMON` topic. This data is sent f
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`. 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 ```javascript
{ // Example message from Executor { // Example message from Executor
"node_id" : "uique-machine-id", "message_type" : "instrumentation",
"node_id" : "unique-machine-id",
"resource_id": "logical-entity-id", "resource_id": "logical-entity-id",
"function_id": "unique-function-id", "function_id": "unique-function-id",
"timestamp" : "time(2) compatible timestamp", "timestamp" : "time(2) compatible timestamp",
...@@ -67,7 +71,8 @@ and whoever needs the data is allowed to read it. Each message is required to ha ...@@ -67,7 +71,8 @@ and whoever needs the data is allowed to read it. Each message is required to ha
} }
{ // Example message from reverse proxy { // Example message from reverse proxy
"node_id" : "uique-machine-id", "message_type" : "instrumentation",
"node_id" : "unique-machine-id",
"resource_id": "logical-entity-id", "resource_id": "logical-entity-id",
"function_id": "unique-function-id", "function_id": "unique-function-id",
"timestamp" : "time(2) compatible timestamp", "timestamp" : "time(2) compatible timestamp",
...@@ -75,7 +80,8 @@ and whoever needs the data is allowed to read it. Each message is required to ha ...@@ -75,7 +80,8 @@ and whoever needs the data is allowed to read it. Each message is required to ha
} }
{ // Example message from dispatch manager { // Example message from dispatch manager
"node_id" : "uique-machine-id", "message_type" : "instrumentation",
"node_id" : "unique-machine-id",
"resource_id": "logical-entity-id", "resource_id": "logical-entity-id",
"function_id": "unique-function-id", "function_id": "unique-function-id",
"timestamp" : "time(2) compatible timestamp", "timestamp" : "time(2) compatible timestamp",
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment