# NOAA Space Weather Alert Monitor — workflow

## Choose this tool

Satellite and communications analysts, GNSS-dependent operations researchers, grid-risk reporting teams and automation builders who need traceable official bulletins.

Useful output columns: `title`, `productId`, `messageCode`, `serialNumber`, `issuedAt`, `observationAgeHours`, `sourceFreshness`, `comparisonStatus`, `sourceUrl`.

## Practical workflow

Run the default to review three recent bulletins and their issue timestamps. Filter by an exact source product ID or a literal term such as radio or geomagnetic. Join the full official bulletin to your own incident workflow; use comparisons to spot source text changes.

## Check the fit

The retained feed is not a complete historical archive and its window can change. A bulletin in the feed is not necessarily still active; validity, extensions and cancellations remain in the original message. No independent hazard ranking, predicted business loss or operating recommendation is generated. Official sources and established emergency channels take precedence for safety decisions.

## Real output sample

One selected row from a 2026-11-21 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links omitted.

Run: pxhYfztsQq0anN2Zv. Summary status: ok. Incomplete: false.

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health.

```json
{
  "recordId": "noaa-swpc:K04W:2026-11-19T01:18:16.670Z",
  "title": "EXTENDED WARNING: Geomagnetic K-index of 4 expected",
  "productId": "K04W",
  "messageCode": "WARK04",
  "serialNumber": "5457",
  "issuedAt": "2026-11-19T01:18:16.670Z",
  "observationAgeHours": 67.06,
  "sourceFreshness": "issued_within_72_hours",
  "comparisonStatus": "not_requested",
  "sourceUrl": "https://services.swpc.noaa.gov/products/alerts.json",
  "url": "https://services.swpc.noaa.gov/products/alerts.json",
  "observedAt": "2026-11-21T20:21:47.727Z"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [Vendor Incident Monitor - Public Outage Feeds](https://mayd-it.com/data-tools/actors/vendor-incident-feed-monitor/)

Place official space-weather advisories beside separately reported vendor incidents.

1. Review issue times, parsed validity and the original NOAA message.
2. Run the vendor incident monitor against selected supported status feeds.
3. Present the observations side by side for operator review with their source links.

Temporal overlap does not establish causation, local disruption or an active incident. Official operator instructions take precedence.

### [GDACS Disaster Alert Monitor - Event Revisions](https://mayd-it.com/data-tools/actors/gdacs-disaster-alert-monitor/)

Build a broader source-labeled situational-awareness dashboard.

1. Export NOAA space-weather messages and their issue times.
2. Run GDACS separately for its supported terrestrial disaster alerts.
3. Keep event type, validity, location scope and source explicit in the combined dashboard.

NOAA space-weather products and GDACS events have different severity scales and geographic scope. Neither feed is a substitute for emergency services.
