Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use API Umbrella Admin API to get Dashboard Analytics #2036

Closed
bajiat opened this issue Feb 6, 2017 · 6 comments
Closed

Use API Umbrella Admin API to get Dashboard Analytics #2036

bajiat opened this issue Feb 6, 2017 · 6 comments

Comments

@bajiat
Copy link
Contributor

bajiat commented Feb 6, 2017

From @brylie on December 12, 2016 13:30

Context

We currently get API Umbrella analytics directly from Elasticsearch via its public HTTP API.

apinf-dashboardelasticdata-methods

API Umbrella 0.14 is planned to disable the public HTTP interface for Elasticsearch by default. This is a security enhancement.

Task

We need to start fetching Dashboard analytics directly from the API Umbrella Admin API. There is a 'drilldown analytics' endpoint that takes several parametrs:

screenshot_20161212_152802

Integration code

In order to support the analytics endpoint, we need to either

  • modify our Meteor API Umbrella package to include a GET method for the analytics endpoint
  • determine a different approach to API Umbrella integration altogether

Copied from original issue: Digipalvelutehdas/APIKA#121

@bajiat
Copy link
Contributor Author

bajiat commented Feb 6, 2017

From @shaliko on December 16, 2016 14:35

After implement that feature we will not need direct connect from Platform to ElasticSearch and can update docker-compose file. At lease drop 2 lines https://github.com/apinf/platform/blob/develop/docker-compose.yml#L14-L15

@bajiat
Copy link
Contributor Author

bajiat commented Feb 6, 2017

From @Nazarah on December 19, 2016 4:0

Will this have any impacts on UI in current APInf?

@bajiat
Copy link
Contributor Author

bajiat commented Feb 6, 2017

@Nazarah It should not make any difference. It affects the server methods for fetching data. Potential impact: removing ElasticSearch from Proxies in settings menu. If something is not available through admin API, that could affect charts and filtering. The current assumption is that the same data would be available.

@bajiat
Copy link
Contributor Author

bajiat commented Feb 6, 2017

@brylie First step is to list what needs to be changed.

@bajiat bajiat added ready and removed planning labels Feb 6, 2017
@bajiat bajiat added this to the Sprint 36 milestone Feb 6, 2017
@brylie
Copy link
Contributor

brylie commented Feb 7, 2017

@bajiat OK, I am auditing the code now.

@brylie
Copy link
Contributor

brylie commented Mar 21, 2017

Closing this issue, since we will likely continue to use Elasticsearch directly for Analytics data.

@brylie brylie removed their assignment Mar 21, 2017
@brylie brylie removed this from the Sprint 36 milestone Mar 21, 2017
@bajiat bajiat closed this as completed Apr 18, 2017
@bajiat bajiat removed the blocked label Apr 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants