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

Research API monitoring options #2129

Closed
5 of 6 tasks
bajiat opened this issue Feb 16, 2017 · 5 comments
Closed
5 of 6 tasks

Research API monitoring options #2129

bajiat opened this issue Feb 16, 2017 · 5 comments
Assignees
Milestone

Comments

@bajiat
Copy link
Contributor

bajiat commented Feb 16, 2017

Check monitoring services and whether they could be integrated with APInf. One of the criteria is a REST API for starting monitoring and getting monitoring data back. Supports multi-level criteria for monitoring, such as thresholds set by API managers. The service must also be fully open source.

Definition of done

  • Research more than one option.
  • Present the results in a comparative document not settling on one of the options.
  • Document must contain pros and cons.
  • Document can contain a recommendation.
  • Document is stored in docs repository.
  • Check and document the license for each option.
@brylie brylie added ready and removed planning labels Feb 20, 2017
@bajiat bajiat added this to the Sprint 37 milestone Feb 20, 2017
@brylie brylie added in progress and removed ready labels Feb 27, 2017
@brylie
Copy link
Contributor

brylie commented Feb 28, 2017

@Nazarah what are some user scenarios we will be testing with the API Monitoring feature? I would like to include relevant information in my research. E.g. if we believe sending SMS messages will be useful, I want to check what Notifications the monitoring solutions support.

@philippeluickx
Copy link
Contributor

Make sure to check #1183

I thought there was an open source component from a competitor, but couldn't find it. There are some github repo's though that deal with API monitoring:

@Nazarah
Copy link
Contributor

Nazarah commented Mar 7, 2017

  1. the following things to consider:
  • server load
  • amount of data coming down (result shown as pagination)
  • encryption level
  • quality of controller code
  • Data and transactions important to API owner / Manager
  • Uptime
  • Concurrent requests to handle
  • API end points.
  • Path of a specific method*
  • Top 50 user connections
  • CPU hours
  • data objects returned per calls.
  1. Should have an Hourband check for the most important things.

  2. Acceptable threshold time.

(resounce: https://smartbear.com/learn/performance-monitoring/guide-to-api-monitoring/)

@brylie
Copy link
Contributor

brylie commented Mar 8, 2017

@Nazarah I have added a few rows to the table, based roughly on your comment.

@brylie
Copy link
Contributor

brylie commented Mar 8, 2017

Also reviewing the Smartbear article What is API Monitoring?

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

4 participants