Hi, Currently we have an 'Availability of APIs' page in the API-M admin dashboard(Image attached) which shows the availability of APIs. In here we have listed each *api_version* with it's availability *status*. Currently the "status" can take values as follows.
1. Available 2. Server error occurred 3. Response count is too low 4. Response time is too high In a discussion with Issabelle it was suggested we should avoid using 2,3,4 as statuses, since they are not actually statuses, but the reason behind the status. We cannot use "unavailable" instead of 2,3,4 since they do not mean the API is unavailable, but those APIs are not behaving normal. There are two points need to be figured out. - The correct wording to use Healthy/Unhealthy Normal/Abnormal - How to show the reason behind the status The initial suggestion was that we could give the user a drill down option to see the real reason behind the status. The UI folks suggested to list the reason(2,3,4) within brackets. We could also change the column name from 'status' to a more sensible name if we could come up with one. Any suggestions? -- Thanks & Regards, Fazlan Nazeem *Software Engineer* *WSO2 Inc* Mobile : +94772338839 <%2B94%20%280%29%20773%20451194> [email protected]
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
