Skip to content

Incident detail

Degraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Export

Resolved incidentMinor

Timeline window

to

Get alerted the next time LaunchDarkly breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    Some customers using LaunchDarkly Observability with AWS CloudWatch Metric Stream and/or CloudWatch Firehose log export may experience delayed ingestion of metrics/logs into Observability. The impact is limited to Observability data ingestion and related dashboards/alerts.

  2. Resolved

    This issue has been resolved. Observability ingestion from AWS CloudWatch Metric Streams and CloudWatch Firehose log export has returned to normal. Data sent during the incident window may not have been ingested, and customers may see gaps in metrics or logs for that period.

Keep exploring

More from LaunchDarkly

Neighboring incidents on LaunchDarkly's timeline and the rest of their record on OutageDeck.