Last updated Nov 2, 2026.
Kibana's Opsgenie connector has a configurable URL, so you can point it at OpsPing's Opsgenie-compatible alert API and keep your existing rule actions: create-alert actions open OpsPing alerts and recovery actions close them by alias.
Before you start
- The Opsgenie connector requires an Elastic Platinum (or higher) license; the connector type declares
minimumLicenseRequired: 'platinum'(source ↗). On lower license tiers the connector isn't available. - If your Kibana restricts outbound hosts with
xpack.actions.allowedHosts, addapi.opsping.com(Elastic's connector docs ↗). - Create an OpsPing API key with write scope. It goes where the Opsgenie key went; Kibana sends it as
Authorization: GenieKey <key>(connector source ↗).
Setup
- In Kibana, go to Stack Management → Connectors and edit your Opsgenie connector (or create one).
- Set URL to
https://api.opsping.com(no path; Kibana appends/v2/alerts). - Replace API Key with the OpsPing key and save.
- On the connector's Test tab, run Create alert with an alias such as
kibana-test, then Close alert with the same alias, and confirm both in OpsPing.
Existing rules keep working once the connector points at OpsPing. Create actions post to /v2/alerts; recovery actions post to /v2/alerts/<alias>/close?identifierType=alias, so keep the alias identical in a rule's create and recovery actions.
What carries over
| Kibana action field | In OpsPing |
|---|---|
| Message | Message (1–130 characters; Kibana truncates longer values) |
| Alias | Alias: dedupes repeat creates and is how recovery closes the alert (up to 512 characters; Kibana hashes longer aliases) |
| Priority | Priority P1–P5 |
| Description, Entity, Source, Details | Same fields |
| Tags | Tags: at most 20, each up to 50 characters, or OpsPing rejects the request |
| Responders (JSON editor) | A team given only by name is rejected, so leave responders out and let OpsPing routing decide, or reference responders by ID |
The full list of supported endpoints, fields and differences is on the Opsgenie-compatible API page.
FAQ
Can Kibana's Opsgenie connector send to OpsPing?
Yes. The connector's URL field is configurable; set it to https://api.opsping.com and use an OpsPing API key. Kibana calls the Opsgenie v2 create and close-by-alias endpoints, both of which OpsPing supports.
Do I need a paid Elastic license?
The Opsgenie connector requires a Platinum or higher license, per Kibana's connector definition. That requirement comes from Elastic, not OpsPing.
Do Kibana recovery actions close OpsPing alerts?
Yes, when the recovery action uses the same alias as the create action. Kibana sends a close request with identifierType=alias, and OpsPing closes the matching open alert.