-
Notifications
You must be signed in to change notification settings - Fork 33
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
Comments
Inspiration can be found with competitors. E.g. https://www.apiscience.com/ |
After discussion with @frenchbread and @NNN we scoped the Epic as follows:
Feature:
Future features:
|
Some other services: |
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. |
@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. |
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. |
deones!!! |
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)
The text was updated successfully, but these errors were encountered: