Atlassian Statuspage (statuspage.io) Monitoring
Last updated - 14 November, 2025
LogicMonitor’s Atlassian Statuspage (statuspage.io) monitoring package leverages the Statuspage API to monitor and alert on the status of SaaS applications with publicly-accessible status data hosted by Statuspage. For more information, see Statuspage from Atlassian.
Requirements for Atlassian Status Page Monitoring
To monitor Atlassian Statuspage services, you need the following:
- A manually created resource for the Statuspage URL
- Manually add your Statuspage host into monitoring.
Note: Services must be manually added as resources into monitoring. (this note may not even be necessary)
- Access to the LogicMonitor Exchange to import all Statuspage LogicModules
In addition, you can have a configured HTTP proxy, set either at the Collector level or as resource host properties.
Note: Resource host properties take precedence.
Adding Resources in Monitoring
Add your Statuspage host into monitoring. Name the resource using the Statuspage service URL. For example, status.logicmonitor.com or eventbrite.statuspage.io. For more information, see Adding Resources.
Import LogicModules
From the LogicMonitor Exchange, import all Statuspage LogicModules. For more information, see the LogicModules in Package. If these LogicModules are already present, ensure you have the most recent versions.
When the LogicModules are imported, the suite automatically associates with resources using the following process:
- The PropertySource runs against any resource named with a Statuspage URL and queries the Statuspage API for a key.
- If a key is found, the PropertySource sets the
auto.statuspageio_keyproperty and adds “StatusPageIO_Key_Exists” to the resource’ssystem.categoriesproperty. - The DataSource associates with resources that contain “StatusPageIO_Key_Exists” in their
system.categoriesproperty. - The Collector queries
[auto.statuspageio_key].statuspage.io/api/v2/summary.jsonfor status data.
Note: You can manually apply the PropertySource to a resource by adding “statuspage” to its system.categories property.
This packge supports HTTP proxy connections. You can configure proxy settings in the Collector configuration or by setting resource host properties. Resource host properties take precedence. For more information, see Configuring your Collector for use with HTTP Proxies.
The following table describes the proxy-related device host properties:
| Property | Value | Required? |
proxy.enable | This package is written to use Collector proxy settings for configured HTTP calls. To enable, add this resource property with the value set to true. Set to false to override the use of configured Collector proxy settings and connect without a proxy. | No |
proxy.host | Configure a proxy host to connect through that is different from Collector configuration. | No |
proxy.port | Configure a proxy port to connect through that is different from Collector configuration. | No |
LogicModules in Package
LogicMonitor’s package for Statuspage consists of the following LogicModules. For full coverage, import the following LogicModules into your platform.
| Display Name | Type | Description |
| addCategory_StatusPageIO_Key | PropertySource | Captures the page’s associated API key and sets the auto.statuspageio_key property. Adds “StatusPageIO_Key_Exists” to the system.categories property. |
| StatusPageIO_Service_Status | DataSource | Monitors status of services monitored by Statuspage and alerts on status of degraded, partial outage, or major outage. |
When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendation.
Recommendation: If necessary, adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Static Thresholds for Datapoints.
