Logz.io: A small number of users are experiencing elevated number of errors on filebeat input
Timeline of updates
- resolved
We've seen very sporadic increase in errors on the filebeat input. After maintenance work these errors have gone below to the normal threshold. We will be monitoring this closely and continue a maintenance task to reduce this further.
From Logz.io’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.logz.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Logz.io, started 2016-06-01 08:38 UTC, resolved after 3.6 h, 1 update(s).
- Title
- A small number of users are experiencing elevated number of errors on filebeat input
- Vendor
- Logz.io
- Date
- URL
- https://rewindex.com/company/logz-io/incidents/y8m1mpbbf1zv
Logz.io profileRecent Logz.io incidentsAll outages on June 1, 2016Logz.io in June 2016MarkdownJSON