Astry offers integrations with standard solutions to trigger incidents. They are accessible from the main Organization tab, then Incoming Integrations. To enable an integration, you must be an Owner within the Organization.
Once enabled, most integrations rely on an API key, generated from the integration page and then used in the URL (or email address) called by your system.
Note: Most integrations let you set, in addition to the title and description of the incident, its priority (from 1 to 5), its tags (used by the routing rules and to link the impacted resources) and a correlationId, used for incident de-duplication.
Elastalert / Elasticsearch / ELK
Astry can interface with Elasticsearch via Elastalert. This component is responsible for anomaly detection (by writing detection rules) and can send alerts to Astry. This integration is relevant when your information system already has an Elasticsearch solution (which, for example, hosts monitoring metrics).
The actual integration procedure is described on the Incoming Integrations page, then Elastalert / ELK.
Emails
You can trigger incidents by simply sending an email. This integration can be relevant, for example, when your customers already report issues to you by email. It can also be relevant if you have a monitoring solution that can send emails (which is often the case), making it a simple way to integrate Astry into your information system.
The subject of the email becomes the incident title, and its body the description. The destination email address is built from your API key, and can carry optional parameters: for example YOUR_KEY+priority=3&tags=tag1_tag2&correlationId=abcd1234@... (tags are separated by _, and the default priority is 3).
The actual integration procedure is described on the Incoming Integrations page, then Emails.
Nagios / Icinga
This integration is only available as a beta for now. On the standard version of Astry, you can instead use the Email integration (see above) to trigger incidents from Nagios/Icinga.
Prometheus
Astry can interface with Prometheus via the AlertManager component. In this case, alerting rules are defined within AlertManager, which triggers incidents on Astry. This integration is relevant when your information system already has a Prometheus solution.
The actual integration procedure is described on the Incoming Integrations page, then Prometheus.
Webhook
Webhook is the simplest way to offer an Astry integration for any application or solution that can make an HTTP(S) call. It simply involves sending a REST request with the incident's parameters in the request body:
curl -XPOST https://api.astry.fr/integrations/api/20220510/alert/YOUR_KEY \
-H "Content-Type: application/json" \
-d '{"correlationId":"MyCorrelationId","title":"My new incident","content":"Incident description","priority":3,"tags":["MyTag"]}'
The correlationId, title and content fields are required. The priority (from 1 to 5, 3 by default) and tags fields are optional.
The actual integration procedure is described on the Incoming Integrations page, then Webhook.
Zabbix
Astry can interface with Zabbix (regardless of version). This integration is relevant when your information system already has a Zabbix solution.
The actual integration procedure is described on the Incoming Integrations page, then Zabbix, with dedicated instructions for Zabbix 4 and for Zabbix 6.
Amazon CloudWatch and Amazon SNS
Astry can trigger incidents from your Amazon CloudWatch alarms, or from any message published to an Amazon SNS topic. Both integrations are detailed on the AWS Integrations page.
Vercel
Astry can connect to your Vercel account to raise incidents from your projects' logs (errors, HTTP 5xx responses, failed deployments, ...). See the Vercel Integration page.
Phone
You can also trigger an incident with a simple phone call, by calling a dedicated number and entering a 6-digit code. See the Phone Integration page.
Monitors
Finally, Astry can itself monitor your HTTP services and raise incidents when they no longer respond correctly. See the Monitors page.