Component-Level Monitoring
Understand how PulsAPI breaks services into individual components and tracks each one independently.
Component-Level Monitoring
Most cloud and SaaS providers are not monolithic — they are made up of many independent components. PulsAPI mirrors this structure by breaking each service into its constituent parts and tracking each component's status separately.
What are components?
A component is an individual subsystem or product within a larger service. For example:
| Service | Example Components |
|---|---|
| AWS | EC2, S3, RDS, Lambda, CloudFront, Route 53 |
| GitHub | Git Operations, Actions, Packages, Pages, Codespaces |
| Stripe | API, Dashboard, Checkout, Connect, Webhooks |
| Cloudflare | CDN, DNS, Workers, R2, Zero Trust |
PulsAPI sources component definitions directly from each provider's status page. When a provider adds or removes components, PulsAPI reflects the change automatically.
Why component-level tracking matters
A service's top-level status might show OPERATIONAL while a single critical component is degraded. Component-level monitoring lets you:
- Detect targeted issues — Know that AWS S3 is having problems even when the overall AWS status page still says operational.
- Reduce alert fatigue — Subscribe to alerts for only the components you actually depend on (coming soon).
- Investigate faster — Pinpoint exactly which part of a provider is affected without reading through status page prose.
PulsAPI derives the overall service status from the worst component status. If any single component is in MAJOR_OUTAGE, the service-level status reflects that.
Viewing component status
On the Service Detail Page
The Component Breakdown section of every Service Detail Page lists all tracked components in a table:
| Column | Description |
|---|---|
| Component name | The name of the subsystem. |
| Status | Current status with a color-coded indicator. |
| 24h sparkline | A miniature trend chart for the last 24 hours. |
Components in a non-operational state float to the top of the list so you can spot problems immediately.
On status cards (My Board)
Status cards on My Board show a compact affected component count (e.g., "3 of 18 degraded") when one or more components are not fully operational. Click the card to expand into the full component view.
Component history sparklines
Each component has its own sparkline chart — a small line graph covering the past 24 hours. The sparkline gives you a quick visual sense of:
- How long an issue has persisted.
- Whether a component is recovering or getting worse.
- Intermittent flapping between states.
Hover over the sparkline to see exact timestamps and statuses at each data point.
Early warning indicators
PulsAPI provides early warning signals to help you anticipate problems before they escalate:
- Rapid state changes — If a component flips between OPERATIONAL and DEGRADED multiple times in a short window, the card displays a warning indicator. This often precedes a larger outage.
- Component divergence — When several components within the same service degrade simultaneously, PulsAPI highlights the pattern as a potential systemic issue.
- Trend detection — Sparklines that show a downward slope over the past few hours are visually emphasized so they stand out during a quick scan.
Pair component-level monitoring with Alerts & Notifications to get notified the moment a specific component degrades — before the provider officially acknowledges the issue.
Next steps
- Service Detail Page — See the full detail view including incidents and SLA metrics.
- Alerts & Notifications — Set up targeted component alerts.
- My Board — See component health at a glance on your dashboard.