Grafana vs Prisma: reliability
In the last 60 days, Grafana had 6 incidents (median fix 58 min) and Prisma had 9 incidents. Grafana broke less often.
Side by side, last 60 days
Grafana's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Grafana: Degraded performance for Grafana Cloud Metrics in prod-us-central-7 | high | 2 h | first | |
| Grafana: Mimir query unexpected response with status code 500 | medium | 9 h | first | |
| Grafana: Elevated query errors for Grafana Cloud Metrics in prod-us-east-3 | medium | ongoing | first | |
| Grafana: Cloud Logs writes - Elevated latency and error rates in prod-eu-central-0 | minor | 20 min | first | |
| Grafana Cloud Metrics Queries Experience Minor Outage and Recovery | minor | ongoing | not yet |
Prisma's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Prisma v8.0.0-rc.18: Breaking Changes in Raw SQL and PSL | high | ongoing | ||
| Prisma v8.0.0-rc.24 MongoDB Date Storage Breaking Change Cause: MongoDB Date storage logic was updated to store Date as a BSON date at midnight instead of a calendar date. | medium | ongoing | ||
| Prisma Dev WAL Polling Enters Aborted Socket Transactions and Breaks Shutdown Cause: Internal WAL/Streams work queries the same PGlite instance while a client transaction is still in an aborted state following an expected SQL error, triggering error code 25P02. | medium | ongoing | ||
| Prisma 6.19.3 Rust-Free adapter-pg Exceeds MaxWait Under Pool Contention | medium | ongoing | ||
| Prisma v8.0.0-rc.23 Released with Breaking Changes for Apps and MongoDB Indexes | medium | ongoing |