Webhooks, deploy events and the read-only API
Three small connections, each signed or token-protected, none of which can change anything in your systems.
AvailabilityAvailable to everyone with early access to Varqeni.
How it works
- Deploy events: your CI posts each deploy (service, version, commit, who). A service that starts failing within 10 minutes of one, with no clean run in between, is named as a bad deploy, with what was deployed.
- Outbound webhook: every incident, page and resolve as JSON to your endpoint, signed so you can check it came from Varqeni, and retried if your endpoint is busy.
- Read-only API: incidents, one incident with its seal check and report, and its timeline. Your administrator makes a token on the Varqeni host; it is shown once and stored only as a hash.
What you should see: Requests are limited per minute, and nothing in the API can approve, change or delete anything. In the Fortis lab a recorded deploy followed by errors was named as the bad deploy with its version, commit and who, and the API answered with a token, refused without one, refused writes, and refused the token once revoked. A page and its resolve reached a test endpoint signed, and a delivery the endpoint turned away was retried two seconds later.
What it can and cannot do
Can
- Take deploy events from your CI and name the deploy that broke a service, and answer read-only API calls with a token. Send every notice, page and resolve to your endpoint, signed and retried.
Cannot
- Approve, change or delete anything through the API, or send a webhook unsigned.
Related articles
- Alerts from Prometheus Alertmanager and other monitoringSend the alerts you already have to Varqeni. Each one opens an incident on the system it is about, with that system's evidence sealed beside it.
- Post-incident write-ups and follow-upsA blameless write-up drafted from the record, ready for you to check, and a follow-up ticket in Jira in one step.
- What Varqeni reads, and what it does notVarqeni reads the state of your pipeline, never the rows of your data.
Still stuck? Contact support or email info@fortisdatagroup.com.