Presentation of service statuses needs to be improved
Description
Currently, REST call for the service status returns this : { "name":"appfabric", "description":"Service for managing application lifecycle.", "status":"OK", "logs":"OK", "min":1, "max":1, "requested":1, "provisioned":1 }, { "name":"log.saver", "description":"Service to collect and store logs.", "status":"OK", "logs":"NOTOK", "min":1, "max":5, "requested":1, "provisioned":1 }, etc
"logs":"OK" and "logs":"NOTOK" seems to be confusing for customers.
Suggest to change this presentation to: "logs":"AVAILABLE" when logs are ready to be read "logs":"NOT AVAILABLE" when logs are not ready to be read "logs":"N/A" for the log.saver specifically
Release Notes
None
Activity
Show:
NitinM June 8, 2020 at 8:28 PM
Closing issues
Won't Fix
Pinned fields
Click on the next to a field label to start pinning.
Currently, REST call for the service status returns this :
{
"name":"appfabric",
"description":"Service for managing application lifecycle.",
"status":"OK",
"logs":"OK",
"min":1,
"max":1,
"requested":1,
"provisioned":1
},
{
"name":"log.saver",
"description":"Service to collect and store logs.",
"status":"OK",
"logs":"NOTOK",
"min":1,
"max":5,
"requested":1,
"provisioned":1
},
etc
"logs":"OK" and "logs":"NOTOK" seems to be confusing for customers.
Suggest to change this presentation to:
"logs":"AVAILABLE" when logs are ready to be read
"logs":"NOT AVAILABLE" when logs are not ready to be read
"logs":"N/A" for the log.saver specifically