Incidentsby GlyphDegraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Export
Feb 10, 07:30 UTCFeb 10, 09:01 UTC
Duration
1h 31m
Impact
Minor
Root cause
Not disclosed
LaunchDarkly, 90 days
9 incidents
Affected
Observability Data Ingest (Sessions, Errors)OpenTelemetry (Logs, Traces, Metrics)Observability (core functionality) - Observability Data Ingest (Sessions, Errors)Observability (core functionality) - OpenTelemetry (Logs, Traces, Metrics)
Final update
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.
Timeline
- Resolved · Feb 10, 09:01 UTC
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.
- Investigating · Feb 10, 07:30 UTC
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.
More from LaunchDarkly
Full historyEmail notifications are not being deliveredlasted 26mdelayed event processinglasted 0mElevated 5xx Errors (15:11–15:32 UTC)lasted 0mDelays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentationlasted 1h 37mElevated error rates in the LaunchDarkly applicationlasted 18h 55mFlag delivery errors in Streaming APIlasted 15m