API detailed view errors display lacking reason for failure in non-machine way

apinf / platform

Apinf - Open source API management platform with multi proxy and protocol support

https://apinf.com/

European Union Public License 1.1

74 stars 33 forks source link

API detailed view errors display lacking reason for failure in non-machine way #3012

Open kyyberi opened 7 years ago

kyyberi commented 7 years ago

Steps to Reproduce:

go to page: https://apinf.io/analytic/4LwTBWzA4opGwJEGZ
scroll down to Error Statistic

Outcome:

Expected Behavior:

Human understandable statement/reason what happened for example with 403: "API key missing", "Nonexisting parameters used". That is what I'm as API manager looking for. It's good to know that something went wrong, but I need more information so I can pass it to API developers if needed.
Downloadable CSV does not contain the reason either

Nazarah commented 7 years ago

We need to investigate if the proxy to which API is connected provides readable reasons along with the error codes. If the information is available, this can be displayed in the UI. Also the downloadable CSV file can have a separate column for the reasons.

marla-singer commented 7 years ago

@kyyberi @Nazarah Elasticsearch doesn't store any information about "reasons" or response message. The list of available fields and values are there http://apinf.org/docs/develop/Integration/Elasticsearch-data-structure/#fields-description

ilarimikkonen commented 5 years ago

yeah. maybe. when time