FAST and restnoded logs / taskID correlation

[paolobeta71]

With FAST via API using the "/mgmt/shared/fast/applications/" endopoint is possible to deploy a new App referencing a FAST template. The returned message includes a TaskID. Ex:

{ "code": 202, "message": [ { "id": "49e7f299-d6eb-4b29-adbf-b11a661a2275", "name": "my_template, "parameters": { "tenant": "Fast", "app": "app105", "virtualAddress": "10.1.10.100", "virtualPort": 443, } } ] }

This taskID can be monitored to check the result or eventually errors. Ex. GET -> /mgmt/shared/fast/tasks/49e7f299-d6eb-4b29-adbf-b11a661a2275

{ "id": "49e7f299-d6eb-4b29-adbf-b11a661a2275", "code": 422, "message": "declaration is invalid\n/Fast/app105/app105_vs/virtualAddresses/0: should match format \"f5ip\"", "name": "", "parameters": {}, "tenant": "Fast", "application": "app105", "operation": "create", "timestamp": "", "host": "localhost" }

The same result or error can be found on the restnoded log but there is not evidence of the taskID. This is not permitting to correlate and check the error after some time when the taskID it is no longer available via API.

This is a request for improvement, in order to track also the TaskID provided via API on the restnoded logs so that for future search it can be used with a simple "grep" and checked afterwards.

[shyawnkarim]

Thanks for submitting this issue. It is now being tracked internally with ID MYSTIQUE-640.

[shyawnkarim]

Closing.

This ticket was included with Release 1.18.0.