Changes / Mezmo / Some logs submitted over syslog using custom ports are not being correctly formatted and are not available for Alerting, Searching, Timelines, Graphs, and Live Tail.
Mezmo: Major incident: Some logs submitted over syslog using custom ports are not being correctly formatted and are not available for Alerting, Searching, Timelines, Graphs, and Live Tail.
Summary
Mezmo reported a major Log Ingestion (Syslog) outage affecting some custom-port logs, making them unavailable for Alerting, Searching, Timelines, Graphs, and Live Tail; logs not using custom ports worked normally. It started at 2022-02-16 19:58 UTC and resolved at 2022-02-16 21:56 UTC (1 h 57 min). A fix was implemented.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Some logs submitted over syslog using custom ports are not being correctly formatted and are not available for Alerting, Searching, Timelines, Graphs, and Live Tail.
Before: not present
After: major
Before: not present
After: postmortem
Before: not present
After: 2022-02-16 19:58 UTC
Before: not present
After: 2022-02-16 21:56 UTC
Before: not present
After: Log Ingestion (Syslog)
Before: not present
After: Some logs being sent to our service over syslog using custom ports are not being correctly parsed and are not available for Alerting, Searching, Timelines, Graphs, and Live Tail. Unparsable log lines will show the error “Unidentifiable Syslog Source” and “Unsupported syslog format.” Logs being sent over syslog that do not use custom ports are working normally.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: The incident has been resolved. If you continue to experience issues with unparsable log lines that show the error “Unidentifiable Syslog Source” and “Unsupported Syslog format”, please contact Support.
Before: not present
After: **Dates:**
Start Time: Wednesday, February 16, 2022 at 19:58 UTC
End Time: Wednesday, February 16, 2022 at 21:10 UTC
Duration: 1:12:00
**What happened:**
Some logs being sent to our service over syslog using custom ports were not being correctly parsed and were not available for Alerting, Searching, Timelines, Graphs, and Live Tail. Unparsable log lines showed the error “Unidentifiable Syslog Source” and “Unsupported syslog format.” Logs being sent over syslog that do not use custom ports were working normally.
**Why it happened:**
We introduced a bug into our production environment, specifically in a new service called Syslog Forwarder. The bug prevented Syslog lines from being parsed.
As a result, any newly submitted Syslog lines sent using custom ports were not parsed. The lines displayed an error “Unidentifiable Syslog Source” and “Unsupported syslog format.”
**How we fixed it:**
We created a hot fix that corrected the bug.
**What we are doing to prevent it from happening again:**
We added to our test suite to guard against regressions in the Syslog Forwarder.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Some logs submitted over syslog using custom ports are not being correctly formatted and are not available for Alerting, Searching, Timelines, Graphs, and Live Tail. (this change) Mezmo reported a major Log Ingestion (Syslog) outage affecting some custom-port logs, making them unavailable for Alerting, Searching, Timelines, Graphs, and Live Tail; logs not using custom ports worked normally. It started at 2022-02-16 19:58 UTC and resolved at 2022-02-16 21:56 UTC (1 h 57 min). A fix was implemented. | Major incident |