2. Why Monitor?
● You need to know if your application is
working correctly
● Set expectations on outages
● Understand what needs to be fixed when
something goes wrong
3. The Problem: Monitoring is Tedious
● Having full monitoring coverage of your
production APIs: internal and external
● Monitors are only created when there is a
failure in production
● No easy workflow to move testing/monitoring
from development to production
4.
5. The Solution:
● Use open source API testing frameworks for
monitoring
● Monitor every single API endpoint and
variations of it
○ GET/POST/PUT
○ Positive and negative monitors
● Deploy new monitoring via GitHub or from a
continuous integration system
6. Produces Key Metrics
● Endpoint Up/Down times
● Response times
● Structure of response is accurate
● Multi global region metric of the above
7. First Open Source Framework Support
● Dead simple to use
● Light weight
● Simple syntax
● Dedicated to REST API testing
13. Auth and Data Security
● OpenStack Keystone project to manage all
tokens and keys
○ Everything goes through this layer
● Data is retained per
○ Tenant
○ Group
○ User
14. Monitor Code Execution
● All monitors code runs in its own container
(Docker.io)
● Code is completely separated from
customers