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

API Monitoring #1183

Closed
bajiat opened this issue Jun 20, 2016 · 10 comments
Closed

API Monitoring #1183

bajiat opened this issue Jun 20, 2016 · 10 comments

Comments

@bajiat
Copy link
Contributor

bajiat commented Jun 20, 2016

This is an EPIC for monitoring API downtime/uptime, alerting owners and displaying the API status to API consumers (in catalog and on API details page)

@philippeluickx
Copy link
Contributor

Inspiration can be found with competitors. E.g. https://www.apiscience.com/

@philippeluickx
Copy link
Contributor

After discussion with @frenchbread and @NNN we scoped the Epic as follows:

  • We prefer to monitor the API, not the host. The host could have an HTTP 200 response with a nice webpage showing "API currently under maintance"
  • Some APIs have an URL where you can ping the status (e.g. https://status.github.com/api) but we assume this will be the minority. In any case, for these to work we would have to do a mapping ("status": "good" vs "up": "yes" vs "ping": 1)
  • Daily ping will do for now, we can always easily adapt later.

Feature:

  • In the form / wizard, the user can add a url that will be pinged daily
  • If no url is added, monitoring is disabled (will show as a grey dot in catalog?)
  • We clearly explain to the API owner what the functionatity is of adding the url: showing the quality of the API to users browsing the catalog + emails when it's down

Future features:

  • Automatically select a default url to ping (that can be changed)
  • Add a "custom" url for status, with mapping

@philippeluickx
Copy link
Contributor

@bajiat
Copy link
Contributor Author

bajiat commented Aug 25, 2016

@philippeluickx
Copy link
Contributor

image

@philippeluickx
Copy link
Contributor

image

image

@bajiat
Copy link
Contributor Author

bajiat commented Sep 6, 2016

Comment from @bajiat and @philippeluickx One option is the approach above: give the owner an option to use API monitoring, but they would need to give the URL which would be monitored. At this stage, we could stick with giving them the option to give a single URL? Allow only monitoring endpoints that don't require authentication. Add authentication in Monitoring 2.0.

@brylie
Copy link
Contributor

brylie commented Apr 20, 2017

@phanimahesh just showed me a package for REST API monitoring that might serve as the basis for our API Monitoring epic:

https://github.com/upssert/upssert

Just a note.

@phanimahesh
Copy link
Member

Though Postman is not open source, they have a command line companion newman which is Apache-2 Licensed. Newman operates on Postman collections which can either be authored manually or exported from postman. The collection specification is open.

Postman the company also provides an api monitoring service in their paid plans, very likely built on newman itself.

Since we need an all opensource solution, a quick option would be to run newman on cron with html reports and build a simple web dashboard to track status and view reports.

@ilarimikkonen
Copy link
Member

deones!!!

@ghost ghost removed the backlog label Oct 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants