diff --git a/docs/clmc-service.md b/docs/clmc-service.md index dac430b319c45fe32c0eade2abfef272c1973802..db3e4c69bb18ba708a30a75875997f18c50c8b8e 100644 --- a/docs/clmc-service.md +++ b/docs/clmc-service.md @@ -187,20 +187,23 @@ with **/clmc-service** so that the nginx reverse proxy server (listening on port * For each service function, there is a field/fields from which an average estimation of the size of a **response** from this service function can be derived. * All the aforementioned fields reside in a single measurement. -* **POST** ***/graph/temporal?from={timestamp-seconds}&to={timestamp-seconds}*** +* **POST** ***/graph/temporal*** - This API method sends a request to the CLMC service to build a graph related to the time range between the *from* and *to* timestamps (URL query parameters). + This API method sends a request to the CLMC service to build a graph snapshot in the time range between the *from* and *to* timestamps. * Request: Expects a JSON-formatted request body which declares the service function chain and service function chain instance for which the graph is built. - The request should also include the service functions that must be included in the graph along with the measurement name, response time field, request size field and - response size field for each service function. The declared fields could be influx functions across multiple fields. + The request body must include the service functions that must be included in the graph along with the measurement name, response time field, request size field and + response size field for each service function. The time range is also declared in the body by the *from* and *to* parameters. + The declared fields could be influx functions across multiple fields. * Request Body Example: ```json { + "from": 1528385420, + "to": 1528385860, "service_function_chain": "MSDemo", "service_function_chain_instance": "MSDemo_1", "service_functions": { @@ -242,8 +245,6 @@ with **/clmc-service** so that the nginx reverse proxy server (listening on port Returns a 400 Bad Request error if the request body is invalid. - Returns a 400 Bad Request error if the request URL parameters are invalid or missing. - * Response Body Example: ```json