Confluence is a web-based corporate wiki (collaboration software). In recent versions, Confluence has evolved into part of an integrated collaboration platform and has been adapted to work in conjunction with Jira and other Atlassian software products, including Bamboo, Clover, Crowd, Crucible, and Fisheye.
AlertOps’ alert management system can be integrated with Confluence to receive and respond to all (predefined status mappings) alerts through email, SMS, push notification or phone alerts. AlertOps would ensure that the alert/job status would reach the appropriate team by using proper workflows, escalation policies and schedules. Based on your ruleset, incidents can be automatically opened and closed, depending on what event happens in Confluence (with respect to Pages, Users, Attachments, Blogs, Contents, Labels etc.)
The above scenario and scope for integration is due to the fact that AlertOps has a very flexible and simple API/Webhook configuration feature that can be leveraged with Confluence’s notification plugin feature
You can send alerts from Confluence (in this guide ‘Page’ Alerts) to AlertOps.
- AlertOps will automatically create an incident when a new alert is received from Confluence when the eventType field contains ‘page_created/page_restored/page_updated’.
- If an alert with status ‘page_created/page_restored/page_updated’ matches an existing Open Alert, AlertOps will recognize the new alert as a duplicate and ignore the alert.
- The alert will be recorded in the Inbound Messages table as “Mapped Appended.”
- AlertOps will automatically close the same incident when an alert with eventType contains ‘page_removed/page_trashed’.
These are examples of just some of the things you can do with Confluence and AlertOps.
