We should be checking performance so if new indexes / better data storage needs implementing then we know.
This would have alerted us in advance to the delays with inserts that caused the issues.
We should be checking performance so if new indexes / better data storage needs implementing then we know.
This would have alerted us in advance to the delays with inserts that caused the issues.
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | Reception123 | T7531 503 Backend fetch failed errors lasting a few minutes | ||
Resolved | Unknown Object (User) | T7532 GlobalNewFiles disabled as caused too many connections to db11 (CVE-2021-32722) | ||
Declined | Unknown Object (User) | T7544 Monitor performance of DB Queries |
Do we not already have monitoring in Grafana that is sufficient enough to know about the mentioned issue/future issues?
Doesn't tell us which query, how often it's being done, via what trigger, how long it took
I honestly don't see of any way to do this that benefits MWE, as any logging would only be accessible by Infrastructure and Reception123, and only actually logging can be done for this. It isn't feasible to do in Grafana (in my opinion).
I'm going to go ahead and mark this as declined per what I said above. However, do reopen if a method to do so can be found.