Mezmo outage, 30 June 2022

Some customers' logs are not currently being processed

Started
Resolved
30 Jun 2022, 22:11 UTC (after 35 min)
Impact
Major
Affected
Log Ingestion (Agent/REST API/Code Libraries), Log Ingestion (Heroku), Log Ingestion (Syslog)

Last update from Mezmo

**Dates:** Start Time: Thursday, June 30, 21:40 UTC End Time: Thursday, June 30, 23:32 UTC Duration: 1 hour and 52 minutes **What happened:** Some log lines for some customers were discarded by our service. The log lines were successfully accepted by our ingestion service, but a downstream service - the parser - removed some of them. All further downstream services, such as Alerting, Live Tail, Searching, and Archiving never received these logs. In some cases, lines were received by Live Tail and were appended with the phrase “\(not retained\)”. The great majority of customers - 94.2% - were unaffected and had no log lines discarded. Approximately 3.5% had a relatively sma...

1 Jul 2022, 22:40 UTC

Read the full incident on the official Mezmo status page

Is Mezmo down now?

This page is the record of one past incident. For the live status, see Is Mezmo down right now? - it reads the official status page every 2 minutes.

Other Mezmo incidents

  1. Impact of AWS Issues

  2. Search performance issues

  3. Problems with Search

  4. Issue with Search

  5. Intermittent issues

  6. Log availability and search performance temporarily degraded

  7. Issues accessing logs in boards and screens

  8. Intermittent Pipeline Service Degradation

All recorded Mezmo incidents