[elasticsearch] Top failed APIs is always empty #1249

brasseld · 2018-05-22T13:29:31Z

Even with HTTP responses with a status code between 500 and 599, there is no data in the top failed APIs.

Seems to be only right for a user with admin privileges.

The text was updated successfully, but these errors were encountered:

Closes gravitee-io/issues#1249

brasseld self-assigned this May 22, 2018

brasseld added this to the 1.15.2 milestone May 22, 2018

brasseld added the type: bug label May 22, 2018

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue May 22, 2018

fix(analytics): Remove extra filter if empty

b1b3fb0

Closes gravitee-io/issues#1249

brasseld mentioned this issue May 22, 2018

fix(analytics): Remove extra filter if empty gravitee-io/gravitee-management-rest-api#404

Closed

brasseld added the status: in review label May 22, 2018

brasseld mentioned this issue May 23, 2018

fix(analytics): Remove extra filter if empty gravitee-io/gravitee-management-rest-api#405

Merged

NicolasGeraud pushed a commit to gravitee-io/gravitee-management-rest-api that referenced this issue May 23, 2018

fix(analytics): Remove extra filter if empty

f6b5811

Closes gravitee-io/issues#1249

NicolasGeraud closed this as completed May 23, 2018

NicolasGeraud removed the status: in review label May 23, 2018

GGui pushed a commit to GGui/gravitee-management-rest-api that referenced this issue Jun 24, 2018

fix(analytics): Remove extra filter if empty

0648655

Closes gravitee-io/issues#1249

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[elasticsearch] Top failed APIs is always empty #1249

[elasticsearch] Top failed APIs is always empty #1249

brasseld commented May 22, 2018 •

edited

[elasticsearch] Top failed APIs is always empty #1249

[elasticsearch] Top failed APIs is always empty #1249

Comments

brasseld commented May 22, 2018 • edited

brasseld commented May 22, 2018 •

edited