Instatus
Your agent works in Instatus with your key, and never holds it.
- 7 days free
- Cancel anytime
- Nothing to install
- Kind of work
- Monitoring and incidents
- How you connect
- API key
- What waits for you
- Nothing, until you turn on asking
What your agent can do there
Read errors, logs and metrics, open and resolve incidents.
- status pages
- incidents
- maintenance
- uptime monitoring
- subscribers
- components
- on-call
- notices
At the provider
Technical details
- Hosts
- api.instatus.com
- Key type
- bearer
- Key goes in
- Authorization
Which calls read, write or destroy
| When | Class |
|---|---|
| GET HEAD ^/monitors(-groups)?/[^/]+/run$ | write |
| GET HEAD ^/monitors/cron/[^/]+(/(start|fail))?$ | write |
Without a matching rule, GET, HEAD and OPTIONS read, POST, PUT and PATCH write, and DELETE and any other method destroy. A recipe rule only raises a GET the vendor changes something with to a write. No recipe rule makes a call destructive.
Token IP filtering
If the provider can limit a token to IP addresses, allow Sallyport's outbound address. The connection form shows it, ready to copy.
Bring a service the catalogue has never seen
Add its web address and your key, and your agent uses it like any of the 827. If your agent runs into a service you haven’t added, it sends you a link.
- 7 days free
- Cancel anytime
- Nothing to install