Statusmage Data Connector

The BigPanda Statusmage data connector collects public SaaS provider status events and brings them into your operational data flow. Statusmage fetches public Atom and RSS status feeds from a bundled vendor registry, optionally includes Microsoft 365 cloud status events, and writes normalized records to the saas_events resource.

With this data in BigPanda, your team can investigate service-impacting incidents using SaaS provider status changes alongside the rest of your operational data.

Key Features

Collect public SaaS status feed events from a bundled provider registry of approximately 250 vendors.
Include Microsoft 365 cloud status events from the Microsoft public status feed.
Normalize service incident details into a single status-event stream for downstream analysis.

Supported sources

Statusmage collects events from the following public sources:

Atom and RSS registry: A bundled registry of approximately 250 vendors, sourced from the connector's data/standard_atom_feeds.csv and data/standard_rss_feeds.csv files. Each vendor is identified by the value in the Name column.
Microsoft 365: The Microsoft public cloud status feed at https://status.cloud.microsoft.com/api/feed/mac https://status.cloud.microsoft.com/api/feed/mac, which covers Microsoft 365, Teams, Outlook, and identity-related services. This source is included by default and can be disabled.

Prerequisites

Before you configure the Statusmage connector, ensure you have outbound network access from the connector to the public status feeds you want to collect, including the Microsoft 365 feed if you plan to include it.

Authentication

The Statusmage connector requires no authentication. It reads public Atom and RSS feeds only, so you do not need to provide credentials, tokens, or keys.

Configuration

Configure the connector with the following options. Each option has a default that applies when you do not set a value.

Option	Default	Description
`services`	All vendors	An allowlist of vendor names to collect, matched against the `Name` column in the feed registry. When omitted, the connector collects all vendors in the registry.
`include_microsoft`	`true`	Whether to include Microsoft 365 cloud status events. Set to `false` to exclude them.
`request_timeout`	60	The HTTP request timeout, in seconds.
`max_connections`	50	The maximum number of concurrent HTTP connections the connector opens.
`lookback_days`	7	The number of days of resolved events to retain. Resolved events older than this window are skipped. Active events are always collected. Resolved events with a resolution older than the lookback window are skipped.

Reduce noise with lookback_days and services

Start with a short lookback window and a focused services allowlist, then widen them as needed. This keeps the saas_events resource focused on the providers your team cares about.

For general information on how the Unified Data Connector handles one-time and recurring syncs, see the Streaming Modes documentation.

Quickstart

You run the Statusmage connector through the statusmage run path. The following flags are available:

Flag	Description
`--services`	Limit collection to the listed vendor names. Maps to the `services` option.
`--no-microsoft`	Exclude Microsoft 365 cloud status events. Equivalent to `include_microsoft` set to `false`.
`--destination`	The destination the connector writes to.
`--dataset-name`	The name of the dataset the connector writes to.
`--request-timeout`	The HTTP request timeout, in seconds. Maps to the `request_timeout` option.
`--max-connections`	The maximum number of concurrent HTTP connections. Maps to the `max_connections` option.
`--lookback-days`	The number of days of resolved events to retain. Maps to the `lookback_days` option.
`--config`	The path to a configuration file containing the options above.

Resources

The connector writes to a single resource.

Resource	Primary key	Description
`saas_events`	`event_id`	Normalized SaaS provider status events.

Records are written to external observability storage at statusmage_data/saas_events/**/*.jsonl on the <cluster>-external-observability-udc location, where <cluster> is your environment's cluster identifier.

Output schema

The connector creates one saas_events record per status event, keyed on event_id. The record includes the following fields.

Field	Description
`event_id`	A unique identifier for the status event. This is the resource primary key.
`service`	The name of the SaaS provider or service the event relates to.
`impact`	The impact level reported for the event.
`statuspage_link`	A link to the provider's status page entry for the event.
`support_link`	A link to a provider support resource for the event.
`details_link`	A link to additional details about the event.
`published_at`	The timestamp when the event was first published.
`updated_at`	The timestamp when the event was last updated.
`status`	The reported status of the event.
`is_active`	Whether the event is currently active.
`title`	The title of the status event.
`description`	The description of the status event.
`location`	The affected location or region for the event.
`end_time`	The timestamp when the event ended or is expected to end.
`collected_at`	The timestamp when the connector collected the event.

Next Steps

BigPanda Unified Data Connector: Learn how the Unified Data Connector brings data into BigPanda.
Unified Data Connector Configuration: Review streaming modes and the connector setup process.
External Observability Sources: Understand how external observability data is stored and used.
Data Redaction with UDC: Redact sensitive information ingested through the Unified Data Connector.

In this section: